Silly Rabbit... Frameworks are for Prototypes

Re:Silly Rabbit... Frameworks are for Prototypes by ricardobeat on Monday November 25, 2013 @12:10PM (#6795286)

The bits and pieces you take also work in a very certain way, Backbone is also just a small collection of them. You can in fact easily piece together a backbone-like framework from small components available on components.io or bower.

Unless it solves a specific problem you have, not using any framework will almost always mean more bugs, brittle code, a less consistent API, lots of documentation effort (or lack of) and a much larger learning curve for people other than yourself.

[ Parent | on HN ]

Re:Silly Rabbit... Frameworks are for Prototypes by Prefinem on Monday November 25, 2013 @12:37PM (#6795482)

While using a framework limits you to that framework. I know this isn't a huge setback, but there are times when it is intolerable, ie. framework forces design patterns that you are not using. But that also works both ways. Sometimes you want to enforce design patterns, and then the framework helps you... Although I would sum that up to a lazy programmer IMO

[ Parent | on HN ]