JS Framework Churn

No. Javascript frameworks/tools change every few months, by the time you finish a project, everything you used has been superseded by something new. Last year's expert is today's luddite. Change at that pace is unsustainable for long term support of applications.

I think it's because around 2015 or so there was a lot happening with front end frameworks, and the sentiment comes from then and people have just not updated their priors since.AngularJS was pretty popular at the time, Angular 2 migration was looming, backbone still existed, jQuery (standalone or paired with both) was going strong, Polymer hit 1.0 and it looked like Web Components might actually be something and useful, React was gaining a lot of popularity, Vue was gaining a small amou

I don't think you can do it. Just pick what you actually work with, and try to stay up on that.Someday, maybe, the churn will slow down. But I wouldn't bet on it. Just about the time JS settles down, WebAssembly will be finalized, and there will be a Cambrian explosion of new frameworks, as developers are freed from the shackles of JavaScript on the front-end and can use better languages. Once again, it will take years for a consensus on best practices to emerge, and a thousand

Frontend churn has chilled out so much over the last few years. The default webapp stack today has been the same for 5 years now, next.js (9yo) react (12yo) tailwind (8yo) postgres (36yo). I'm not endorsing this stack, it just seems to be the norm now.Compare that to what we had in the late 00's and early 10's we went through prototype -> mootools -> jquery -> backbone -> angularjs -> ember -> react, all in about 6 years. Thats a new recommended framework ever

The article opens with:>Frameworks, libraries, package managers, guidelines… even languages and meta-languages themselves are changing so fast that there's little to no chance a common or standard way of building applications emerges....and then gives an example using React, JSX, and ES6 modules. This is just my opinion but I think React + JSX will look about as antiquated and irrelevant as jQuery in less time than it took jQuery to lose favor among web developers, rendering the ar

I'm all for shitting on the JS ecosystem, but honestly there haven't been any noticeable shifts whatsoever in its ecosystem for at least 6 or 7 years now.Both React and Vue.js are now older than jQuery was when both were released. Same for Babel and Webpack. Typescript is older than all of these. SASS/SCSS also older than Typescript. Those are the only things you see in 99% of the frontend job descriptions out there.If anything, frontend is kinda boring, and it can be argued

I don't think anything we do today will be the same in a few years. The JS ecosystem is a hack on top of a hack. Typescript itself is a third party add-on usually compiled by a fourth-party builder integrated by a fifth-party bundler. There's no guarantee of stability there, and odds are the whole stack will continue to mutate.I used to love AngularJS v1, but that died a quick death and v2 was much more complicated. React took over but was such a limited library in comparison. I

"We switched from X to Y and we are never going back."I think I've seen thousands of combinations for X and Y on HN. First everyone switched from JS to JQuery, Then JQuery to Ember or Backbone and never looked back. At one point everyone moved from Ember to Angular and never looked back. Then from Angular to React. Some people even switched from Swift and Java to React Native and never looked back. Then from Flux to Redux. And now I see people switching from React to Vue.js (an

> You're so concerned with development speed, yet you're rewriting the same thing in a new framework every 2 years.I think that meme gets thrown around a lot, and it used to be true, but the framework churn of JS has largely stopped at this point. A lot of us (me included) have been just using the same stack for several years now.Sure, React has evolved since 2015/2016 (e.g. the move to function components and hooks) but the old code still runs, with minimal to no changes

I think the biggest problem is that js is way faster charging than almost every other language.I was used to use vue, there was webpack now it's vite or nextjs, some tools are build on top of others like nextjs on webpack and vite on esbuild.If you stop working 2 years in js your tools will completely change.E.g. java has maven and more and more use graddle, but it's way slower change.