Use whatever tool gets the job done.
Use whatever tool gets the job done.
I completely agree, but would you write an article titled "Spoons still blowing away Forks in digging holes"?
It would be far better to state the metric they're using, i.e. "GitHub Stars !== Usage: React downloads still surpass Vue and Angular"
It's taken React about 2-3 years to go from being head to head with Angular(JS) to being the dominant frontend ecosystem. I expect within 2-3 years Vue and React will be on far more equal footing in terms of usage and jobs. (Assuming something else doesn't come along and topple the current trend towards reactive frontend tools.)
I don't think this is true, primarily because of the number of large companies getting behind React and contributing to the ecosystem. Also, the difference between Angular and React is much larger (IMO) than the difference between React and Vue, which means there is less incentive to move to Vue if you already know React because the latter is Good Enough™.
I suppose two factors:
- The scale/"startups = growth" tenet of Silicon Valley/Wall Street trickling down to micro business decisions — pick as many of (whatever is most popular | comes from Massively Scaled Company | used by companies trying to Massively Scale | growing in popularity fast) as possible
- Feedback loop of bosses/managers who make technical decisions based on hirability/availability of paid long-term technical support/brand name (In 2018, nobody ever gets fired for choosing whatever is the equivalent of IBM now)
That's the problem: there are so many tools/frameworks/libraries etc. with so much overlap that people don't know what tool is for what job anymore. And there might not be a real answer to that. When you have a situation like this, people tend to use proxy measures like github stars to figure out what tool to use. Sure, it might not be the right tool, but it's at least picking a tool, as opposed to being locked in constant confusion about which path to take. Sometimes the right tool is the tool you have.
An unmaintained lib might not become a problem or it could become a major obstacle down the line. It's a gamble.