5 ms·
I agree that they're very different, but at the same time, there's a non-trivial base of users who earnestly believe that when you're picking a JS framework to
by bmelton 8y ago
I agree that they're very different, but at the same time, there's a non-trivial base of users who earnestly believe that when you're picking a JS framework to use for <insert whatever>, momentum is a meaningful factor in it.
Obviously, it rarely makes sense to select a framework that is completely disused, or unsupported, but there are articles out there by reputable sources who assert that if you're not using the current hotness, you're going to miss out on every new tool that crops up in the ecosystem, and your startup will languish and die as a result of having to spend so many more cycles just to keep up with what other people can 'npm install'.
What's worse is that they're not entirely wrong. Any good plugin for Vue right now is going to show up in React or Angular post-haste, if it doesn't exist there already.
Edit: I also can't help but wonder how many people saw this article, clicked the link, realized it was based on stars, and then went and starred Vue (exactly as I did). Every time I refresh, Vue is closer to 'toppling' React (at least according to these nonsense metrics)
- taylorswift_ 8y ago> What's worse is that they're not entirely wrong. If your startup dies because of your choice in javascript framework, you were doomed from the get go.