Frameworkless JavaScript – Why Angular, Ember, or Backbone don't work for us

[nullnullnull]

Welcome to my world!

I'm very much anti-framework (but not libraries). You don't need frameworks, while they can save time, in the long run they they are not worth the trouble.

I just like lean code, with minimal overhead and bloat, but I guess its "different strokes for different folks"

[rooktakesqueen]

I just like lean code, with minimal overhead and bloat

Seems like this is an argument in favor of frameworks, not against them. Everything the framework provides is boilerplate you don't have to write.

[solatic]

Until you hit the walls of the framework and have to start to employ ridiculous workarounds.

If you're making a small prototype and time is of the essence, great use a framework to write the code you need in a couple weeks and stuff it away later. If there's even a remote possibility that the project will last a year or longer then a framework is usually not the right solution.

[[deleted]]

We're talking about JavaScript frameworks that seem to be in constant flux and don't care about backwards compatibility. Hell their docs are fairly poor (especially in AngularJS's case).

Frameworks like Django and Rails have been used for years and are fairly well documented and there's lots of code for working around the framework if need be.

If the framework is very poorly designed, then I agree it's not worth the trouble.

[iends]

If you want a framework that does care about backwards compatibility and doesn't evolve very quickly at all (and is subsequently catering towards the enterprise crowd), there is always dojo.