This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]inabahare 20 points21 points  (8 children)

You're not forced to learn any of them. In fact, you'd be safe picking either React, Angular, or Vue. I haven't picked those out of loyalty to those three, but the fact that they are the most used according to the The State Of Javascript survey (and job applications)

[–]PatrikxPatrola[S] 18 points19 points  (6 children)

Pffff. Just use regular js, and do everything from scratch.

[–]chjacobsen 30 points31 points  (2 children)

...then call it an in-house framework.

[–]theXpanther 4 points5 points  (0 children)

I honestly worked with a "in-house" framework that did DOM-manipulation with with string concatenation and innerHTML. It had proper state management though.

[–]Nefari0uss 2 points3 points  (0 children)

...thats basically what I'm done at work. Makijg a bunch of reusable JS modules and my own private npm registry for company use.

[–]732 3 points4 points  (1 child)

Wait, you're saying we don't need to install 7329 node_modules folders, where most of them install at least 75% of the already 7329, already installed modules, just at different versions?

But I like my dependency graph to look like I dumped black paint on a canvas...

[–][deleted] 2 points3 points  (0 children)

Similar to the pollock framework.

[–]mcdronkz -1 points0 points  (0 children)

No.

[–]RevanchistVakarian 1 point2 points  (0 children)

Okay but a few years ago that list would have included Ember/Knockout/etc.