From: Uncle Dee <uncledruby@...>
Date: 2006-03-02T22:51:51+09:00
Subject: Re: ASP.NET 2.0 vs Ruby On Rails

------=_Part_9298_7823325.1141307494395
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

I happen to be the lucky (or unlucky depending POV) reviewer of one ASP.net
2.0 book soon to come out by Manning. I can say with my experiences in doin=
g
exercises and also having built one full-working .NET web-application that
the choice comes down to comfort level, scalability and the number of peopl=
e
involved. RoR has a learning curve, learning ruby. ASP has a learning curve
also, yet you seem to already use it. RoR's ActiveRecord and MVC design mak=
e
doing things in a fast-organized way fairly efficient.


The new features in ASP 2.0 though do have their merits. Both systems offer
Object oriented approaches. The Visual Studio IDE is also a very compelling
selling point for those who feel they work most efficiently in a very
elaborate IDE. I was surprised at times how easy some things were to do. I
do notice a lot of websites touting the easy drag-and-drop or cut-and-paste
ASP solutions are not very efficient however.

Rails is robust and fast for development. I basically mean that it's easy t=
o
get projects from nowhere to someplace quickly and without the hassle of
fighting the language. The real roadblock like I mentioned, is learning the
ruby language. If you're already cozy with ASP, decide what it is that
frustrates you the most about it and see how little frustration you
experience doing the identical tasks using RoR. And, like previously
mentioned, this would be better suited for the RoR mailing list.

Best Regards

------=_Part_9298_7823325.1141307494395--