Re:A Comparison of Angular, Backbone, CanJS and Ember
by marknutter on Wednesday April 17, 2013 @01:27PM
(#5565744)
> I have been burnt by enough frameworks both picked by me or others that promise the world
I've definitely been there, too. I think it's one of the risks in using a framework, but like everything you have to weigh the risks against the rewards.
> I guess a good framework is one that is extensible and straddles the border between a framework and library.
I think Rails did a good job with this. It provides opinionated defaults but allowed people to swap in other libraries as they needed.
I think you are right. I have been burnt by enough frameworks both picked by me or others that promise the world ('really easy, just use this framework! here is an example of a thing X that we did for a demo that kind of looks like something you might want to do').
Then as soon as you do something not anticipated or unimplemented yet in the framework you hit a wall and decelerate from 100 to 0 pretty quickly.
I guess a good framework is one that is extensible and straddles the border between a framework and library.