3 ms·
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
by acemarke 5y ago
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)
- pcthrowaway 5y agoI 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.
- gunshowmo 5y agoAgreed completely. I'm surprised someone deemed this fit to publish. The entire post seems to miss the point of UI frameworks and libraries entirely.
- noahtallen 5y agoThe 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.
- 3np 5y agoWith the author’s reasoning, TypeScript developers would already not be needing Angular, React, or Vue. It’s a bit like claiming that a new version of systemd would make KDE obsolete.
- errantspark 5y agoWhile 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.