Ruby on Rails? Not for us, for now.

October 19, 2005

After a very hard decision-making process, we’re going to hold off on switching to Ruby + Rails for now at The Devine Group.

Primary factors:

  1. Apparent lack of or difficulty in implementing cookieless apps (we need it for our assessments)
  2. Lack of adequate charting components (we need for our reports)
  3. Lack of internal knowledge of Unix-based deployment (Apache, FastCGI, etc.)
  4. Lack of internal knowledge of Ruby
  5. Internal resistance to switching from Microsoft platform (old dogs, new tricks)

I won’t go over all the things that impressed me about RoR, the list would be too long—I’m going to keep my eye on it and I’m not ruling it out for future development projects.

Ruby On Rails vs .NET

October 08, 2005

Well I’m getting sold on Ruby on Rails—My background: I started with implementing Perl scripts, then PHP, then ASP, most recently ASP.NET. In some ways it seems a step back to go to UNIX-based web tech, in other ways it feels a step forward (Agile, Design Patterns, Ruby’s highly OO nature, Test-Driven Development, Ajax, etc.) Anyone else make the jump from ASP.NET to RoR who regretted it + moved back to ASP.NET? I haven’t read many posts out there from people who went to Rails (actually built something) who reverted back…