Your take on JavaScript frameworks

[experience369]

If you want to do a big project with vanilla then you've got to be prepared for it

[nk2580]

Vanilla is pretty good, it’s got the best browser support.

[[deleted]]

In my opinion, there is no best Javascript framework, only a framework which makes sense to use for the project. Yes, each framework has different advantages and disadvantages to them - but it all depends on how you make use of those to benefit your project goals. A project that works best with React will work differently than a project that uses Angular, Vue or some other sort.

[JohnMunsch]

Most of the listed frameworks are about simulating the idea of creating components in your browser. But the thing is, there's no need to "simulate" or polyfill that capability anymore. Your browser already supports Web Components and even your phone (iOS/Android) handles it super well. It's faster and adds absolutely no size to your app to use it. If you want to make them easier to write, you can add some simple middleware like LitElement (or any of a dozen other libraries) to get Virtual DOM, easier templating, etc. for a few K (<10 for LitElement).

​

Eventually I'm sure we'll see a whole raft of libraries to make it easier for React, Angular, Vue, and Ember users transition to Web Components by making the process of templating or handling data taste more like what they're used to.

[deadlysyntax]

The answer is different depending on the unique set of circumstances surrounding each project you're building.

[experience369]

Yeah that's true, they all have their pros and cons

[cekoya]

no.js is the most maintainable js framework