Re:Ruby Frameworks? Which one? Bye bye Rails.
by tkahn6 on Tuesday January 31, 2012 @11:24AM
(#3533906)
> We adopted it. It turned out to be poorer than Rails for our use cases.
Yep I had this exact revelation with a project I was working on. About half way through implementing my own general-purpose validation function and REST/CRUD routes for my models I admitted to myself that I was wasting time. These things are solved problems. I have a much greater appreciation of Rails as a result.
I use Sinatra as a quick way to put a web interface on top of Ruby code, Rails for any non-trivial CRUD paradigm web application.
You didn't say "break new ground", you said "younger developers".
You didn't say "pick and choose", "risk and reward", you said "resistent to adoption" and "conservative".
And you said it on a thread mostly populated with people who used Sinatra --- we weren't "resistent" to Sinatra (I was seduced by it). We adopted it. It turned out to be poorer than Rails for our use cases. Given two options, one of which was better than the other, we used the better option; that's engineering.