3 ms·
ES6 a.k.a. ES2015 came out six years ago, and yet the article keeps on referring to ES6 in the present or future tense. I had to double-check the article to mak
by dry_soup 5y ago
ES6 a.k.a. ES2015 came out six years ago, and yet the article keeps on referring to ES6 in the present or future tense. I had to double-check the article to make sure that this really was written in 2021. The references to Redux and Flow feel similarly dated, now that React hooks are widely used.
I also just don't see how any of the ES6 features named in the article negate the need for a framework like React. React et al. are built on the DOM API more than any individual language feature.
All in all this article feels very confused.
- onion2k 5y agoES6 was specified years ago, but it's not available everywhere. That's why we still use bundlers/transpilers. We're getting to the point now in browsers and Node where all of ES6 works without a compile step. Mainly because IE is finally, properly dead.
- franciscop 5y agoThe article is conflating EcmaScript with the browser APIs. Some browser APIs made jQuery unnecessary in some cases, like `querySelectorAll()`. The "next generation" browser APIs like ShadowDom are not even mentioned; they are effectively trying to do what jQuery => DOM APIs did but with React/Angular/etc => Shadow DOM, but failed at doing so spectacularly. THAT should have been the focus on an article titled "Does modern Javascript make frameworks obsolete?" and not whatever this is. I expected at least a modicum of quality from an official StackOverflow post, but it's so wrong in so many levels that I can only but flag it.
- justsomeuser 5y agoSeems like they do not have a lot of experience actually using JS.