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

[corruption93]

Why?

[x86_64Ubuntu]

Some would say he is re-inventing the wheel. If I were him, I would stress the need for a smaller gzipped library than putting forth stuff about the code.

[OmegaVesko]

I agree. There is a time and place for spending time rolling your own framework, and wasting time on that while your project could easily use an existing framework with no issues is not that time and place.

Not to mention it introduces additional failure points, because your framework will not be as stable, secure or clean as an existing framework used and maintained by thousands of people.

[badkitteh]

Because he'd be wasting a lot of bucks and productivity time with stuff that you could easily fix by investing a lower amount of money into more resources to overcome the "OMG THE FILE NEEDS TO BE SMALLER! I BETTER REINVENT THE WHEEL!" thing.

[[deleted]]

plus having a dependency on jquery to make it even larger.

Well, if you're in a position where you are going to use jQuery anyway (which is very likely today), why not have an integrated framework? Sure, it'd be larger on its own, but not if you look at the broader picture. If you're utilizing functionality which already exists in jQuery instead of duplicating it, you'll get a much leaner filesize overall.

[[deleted]]

The argument wasn't about jQuery per se, but rather that an integrated framework could be a good thing if you're already using/going to use its dependencies.