Ruby on Rails hype: the party is over
Monday, September 24, 2007
Finally it seems that Ruby on Rails is starting to show its real face. Two years of RoR development put into the trash. Wow! Being seven times more productive than Java that means fourteen years of development! Seriously, it's not common to hear of failures of a new and cool software stuff -you can look stupid- so I guess this is the peak of the iceberg of Ruby On Rails projects. In my opinion, Ruby on Rails failed in this project because when dealing with the very small details of a project (that 5% of the project that takes 90% of the time) RoR convention over configuration approach fails. This, and of course integration with legacy systems (considering a database a legacy system). It's clear that any other general purpose language and framework (JEE, .NET) can solve the integration problem better and faster.
3 comments:
With ActiveRecord u can never model a complex domain. I just wonder how long RoR will remain a great framework for simple CRUD applications. Incidentally I also blogged on the same subject today.
I prefer the approach of Grails using a supervitaminazed version of Hibernate POJOs. I agree with both of you about what fails in ActiveRecord: it's hard to use with complex models.
Personally I never liked Active Record. Your code should be able to tell you what rows are in a table without your having to resort to SQL statements. While superficially AR is nice, in practice... it doesn't save you any time.