4 ms·

We have a winner. There are so many JavaScript libraries and frameworks because there's so much JavaScript being written. It has nothing to do with anything abo

• sli 7y ago
  I'd be willing to bet that a massive number of frameworks, especially the smaller ones, start out as something a dev writes for themselves to use in an app, then just decides to release it because why not. That's a good bit different from (and a lot more realistic than) concerted efforts to just pump out new frameworks in isolation just because. I generally see the whole "framework paralysis" as being fairly artificial and more just a convenient complaint to make. React/Angular/Vue have the enterprise space pretty well covered and you'd be more or less fine just picking one of those by throwing darts at a dartboard, unless you already have a preference for paradigm or style, in which case just pick the one that fits. These things are mature, after all. And the first two are backed by companies with huge vested interests in the frameworks being good, as they presumably dogfood them to hell and back. Beyond that, I feel it matters much less what you use. But still, the general idea of just picking the one that best matches how you think about writing an app is still workable advice. It isn't like you have to look into every single framework ever, you just check out ten or so major ones.