This post is entirely nonsensical, and I'm confused how something like this ended up on StackOverflow's blog.
Language syntax has nothing to do with framework features, and especially things like writing UI components, managing state, and updating the DOM. The fact that the major frameworks have continued to explode in usage, and that we've seen new frameworks like Svelte and Solid come out, clearly says that the answer is "no".
Plus, why in the world is the post talking about "with the release of ES6", when that came out 6 years ago? I wondered if this was somehow a repost of something that had been written back in 2015, but a search on a couple phrases didn't turn up any other hits and the post does link to some other SO blog posts from 2017-18.
If I didn't know better I'd swear this was an April Fool's joke or a parody.
(and now that I scroll down further, it looks like the same thing's been said in the comments of that post)
I wonder if this is an AI-generated article. It shows so little understanding of the actual macro-trends while stringing together a bunch of related topics and definitions, I don't think it could have been written by an actual human.
The other thing is that even if ES6 wasn’t already widely released and supported, developers already use upcoming syntax via transpilers. So even if this article was written several years ago before ES6, devs were already using ES6 syntax alongside the popular frameworks.
While I mostly agree with you on this post being ridiculous and anachronistic but I will contend you on:
> Language syntax has nothing to do with framework features, and especially things like writing UI components, managing state, and updating the DOM.
Think of how much less useful jQuery is in 2021 than it was in 2008. That's largely because the language has advanced. The set of things that a framework has to solve has shifted because a larger set of those things can be consistently and easily handled by the language itself.
These days most of what a framework does is give a consistent approach to allow for simpler collaboration. Maybe an argument could be made for building against a framework in order to easily access plugins or things like react native? I almost never use frameworks of any kind anymore and I think a solid style guide could replace the value of a framework in many cases.
I really love programming without pre-processors or compilers. It feels so much more immediate and clear. I think the browser is not just acceptable, but is really good these days.
One thing I have found among junior devs is they will know React really well but not remember things like how the box model works or basic HTML elements like the <br /> tag. This leads to all sorts of frustrating code for everyone.
What I would like to see is more designers writing pure HTML and CSS instead of working in vector editors. Our designs will get better when they understand what HTML is good at. I think custom HTML components are a great start to this.
> Every time JavaScript goes through a major update, we seem to repeat the same cycle. At first, developers are delighted by the new features. They move back to coding directly in JavaScript, and frameworks become less popular. Then, in the relatively long periods between releases, frameworks begin to offer new features and tempt developers back. Repeat.
The other commenters are covering this a bit already, but even the first paragraph just isn’t a true statement at all. Projects don’t suddenly abandon frameworks and rewrite their frontend stack whenever new ES syntax gets released. That’d be incredibly counterproductive.
9 comments
[ 3.5 ms ] story [ 35.7 ms ] threadLanguage syntax has nothing to do with framework features, and especially things like writing UI components, managing state, and updating the DOM. The fact that the major frameworks have continued to explode in usage, and that we've seen new frameworks like Svelte and Solid come out, clearly says that the answer is "no".
Plus, why in the world is the post talking about "with the release of ES6", when that came out 6 years ago? I wondered if this was somehow a repost of something that had been written back in 2015, but a search on a couple phrases didn't turn up any other hits and the post does link to some other SO blog posts from 2017-18.
If I didn't know better I'd swear this was an April Fool's joke or a parody.
(and now that I scroll down further, it looks like the same thing's been said in the comments of that post)
The entire post seems to miss the point of UI frameworks and libraries entirely.
It’s a bit like claiming that a new version of systemd would make KDE obsolete.
> Language syntax has nothing to do with framework features, and especially things like writing UI components, managing state, and updating the DOM.
Think of how much less useful jQuery is in 2021 than it was in 2008. That's largely because the language has advanced. The set of things that a framework has to solve has shifted because a larger set of those things can be consistently and easily handled by the language itself.
These days most of what a framework does is give a consistent approach to allow for simpler collaboration. Maybe an argument could be made for building against a framework in order to easily access plugins or things like react native? I almost never use frameworks of any kind anymore and I think a solid style guide could replace the value of a framework in many cases.
And it makes 0 sense to compare usage of a framework with some arbitrary extra features of a language.
You could at least say the more features we have in the js std lib the less random crap people will insert from their package manager.
https://github.com/lindseymysse/custom-html-element/blob/mai...
This is my favorite feature in HTML / ES6.
I really love programming without pre-processors or compilers. It feels so much more immediate and clear. I think the browser is not just acceptable, but is really good these days.
One thing I have found among junior devs is they will know React really well but not remember things like how the box model works or basic HTML elements like the <br /> tag. This leads to all sorts of frustrating code for everyone.
What I would like to see is more designers writing pure HTML and CSS instead of working in vector editors. Our designs will get better when they understand what HTML is good at. I think custom HTML components are a great start to this.
The other commenters are covering this a bit already, but even the first paragraph just isn’t a true statement at all. Projects don’t suddenly abandon frameworks and rewrite their frontend stack whenever new ES syntax gets released. That’d be incredibly counterproductive.