Yet another JS framework. This time around... Ruby-flavored Vue.
On one hand, people should absolutely go where their passion projects take them. Building languages and compilers is often a critical step on the path of deeper understanding.
However, there's no way to get past the fact that there are too many front-end frameworks that offer same-but-different syntaxes. Most of these have no chance of achieving a large enough ecosystem, but every framework demands reinvention of everything all over again.
It pains me to consider how much smart person energy is currently channeled into creating flavor of the day JS instead of building stuff with whatever tech they are already proficient with.
Case in point: I am MUCH more excited by the Scrimba screencasting platform than I am by the prospect of spending an open-ended amount of time learning another, not-obviously-better framework.
> It pains me to consider how much smart person energy is currently channeled into creating flavor of the day JS instead of building stuff with whatever tech they are already proficient with.
I always thought `diversity is good`, but maybe in certain instances it's not. Perhaps a certain saturation level is reached and diversity just adds noise to the system and causes enormous overlap and your "smart person energy" is mostly spent re-inventing the wheel
Are we allowed to make thinly veiled gestures towards the 2020 Democratic candidate lineup? I don't want to get hell-banned.
Honestly, after React, Vue, Angular, Ember, Stimulus, Meteor and Backbone, how does anyone truly have time to learn learn about Svelte, Marko, Knockout, Aurelia, Riot, Omi, Foundation, Catberry, Composer, Yo-Yo, Vomit, Mithril, Polymer, Sencha... I'm not making a single one of these up. I know that I'm forgetting at least a half-dozen.
Note: try Stimulus!
Seriously though, if you're following every development on more than two JS frameworks, you are procrastinating, lying to yourself and not achieving your full human potential.
The very situation you are describing explains why many of us have avoided working in the web ecosystem entirely for the last 20+ years or so, and don't miss it at all.
Many people thrive in these kind of frenetic, fast changing environments. Others (myself included) don't.
Punchline: my top-level comment was downvoted with an angry passion. My interpretation is that there is a silent mob of people here that are so threatened by the idea that the only thing they know might not be God's Ultimate Solution that anyone who suggests that things were a lot better a decade ago is to be punished.
All I know is that after I help my friend with her React stuff, I go back to Rails and thank my lucky stars.
On one hand, people should absolutely go where their passion projects take them. Building languages and compilers is often a critical step on the path of deeper understanding.
However, there's no way to get past the fact that there are too many front-end frameworks that offer same-but-different syntaxes. Most of these have no chance of achieving a large enough ecosystem, but every framework demands reinvention of everything all over again.
It pains me to consider how much smart person energy is currently channeled into creating flavor of the day JS instead of building stuff with whatever tech they are already proficient with.
Case in point: I am MUCH more excited by the Scrimba screencasting platform than I am by the prospect of spending an open-ended amount of time learning another, not-obviously-better framework.