This week's book giveaway is in the OCAJP forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide 1Z0-808 and have Jeanne Boyarsky & Scott Selikoff on-line! See this thread for details.
Would you please share with us your impressions about Rails?
I reading Rails in my free time.
IMHO, Rails absorbs Java frameworks until the last drop (something Rails folks never admit).
I met a lot of Rails programmers and I was shocked to see their ignorance about Ruby itself.
It looks many programmers learn Rails without learning Ruby itself in the first place.
But the secret sauce is the Ruby language itself which it is beautiful and flexible.
I think RoR is really great until you try to do something against the framework's wishes, then it's a nightmare. I'm hoping Rails 3 will fix some of it, or at least make things more amenable to customization.
David Newton wrote:I think RoR is really great until you try to do something against the framework's wishes, then it's a nightmare. I'm hoping Rails 3 will fix some of it, or at least make things more amenable to customization.
I can't recall experiencing this. Are you thinking of any specific examples, David?
I needed to use a different templating engine (long story) adn wanted to tie it in to the existing mechanisms. Back then there was a bunch of hardcoded stuff revolving around that (which types were supported or cached or something, I forget what) and I would have had to change some RoR guts to get what I wanted, which I really didn't want to do. Changing the validation mechanism was similarly convoluted.
It shouldn't take much effort to find other tales of woe--issues hit while trying to do things in something other than the "Rails way" abound. Sometimes the problem can be restated in a way that allows a clean solution, other times monkey patching is the only way.
Jeremy McNally had some interesting notes on validations in Rails3 Some of the key items: ability to move validations out of the model with custom validators, shorthand for multiple validations dubbed "sexy validations", and moving validations out of ActiveRecord into ActiveModel.
Overall, the merge with Merb means that Rails3 will be a much more open framework in terms of ORM, templating, JS Frameworks, and generally going around/slimming down Rails. This slideshow hits on some of the key points. As the author noted, Rails is now "Less Opinionated" (and more flexible).
Yeah, I'm hoping that particularly with the merge it'll be a bit more like a framework I *really* like, instead of one I generally-like-for-some-classes-of-problems. I also saw those validation comments--definitely more along the lines of what I'd prefer.