Lead Developer, business owner, US Army veteran. I build things for the web. My website is a bunch of HTML pages that didn't need a framework. Yours can be too!
I mean... I hope so? These articles are probably going to come out sooner. I don't hate frameworks (angular guy for the last 5 years here), but they are becoming unneccesary now with the changes to the W3C spec (not new frameworks, but the underlying tech).
I haven't imported jquery into a project in about 3 years because jqlite in angular was plenty. If I'm writing a small page with a few DOM manipulations that requires IE11 support? Sure I'll pull it in.
New projects should be looking hard at web components and how to eliminate the big frameworks, because smaller a la carte libraries are the direction we're going. Just like the best parts of jquery are incorporated into the spec, the best parts of frameworks are starting to be implemented. It's 2018 and I could write a 'Why I don't use Angular' post. I wouldn't, because I think the polyfills are too necessary to say web components are easier than a framework... but that time is coming, it's necessary for the maturation of the ecosystem out of 'new frameworks every hour' and I think it's a sign that we're (hopefully) getting away from the stagnation of JavaScript fatigue into a more stable world where tech is driven by the spec, and not by how a framework writer wants the spec to look like... just my two pennies on it :D
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I mean... I hope so? These articles are probably going to come out sooner. I don't hate frameworks (angular guy for the last 5 years here), but they are becoming unneccesary now with the changes to the W3C spec (not new frameworks, but the underlying tech).
I haven't imported jquery into a project in about 3 years because jqlite in angular was plenty. If I'm writing a small page with a few DOM manipulations that requires IE11 support? Sure I'll pull it in.
New projects should be looking hard at web components and how to eliminate the big frameworks, because smaller a la carte libraries are the direction we're going. Just like the best parts of jquery are incorporated into the spec, the best parts of frameworks are starting to be implemented. It's 2018 and I could write a 'Why I don't use Angular' post. I wouldn't, because I think the polyfills are too necessary to say web components are easier than a framework... but that time is coming, it's necessary for the maturation of the ecosystem out of 'new frameworks every hour' and I think it's a sign that we're (hopefully) getting away from the stagnation of JavaScript fatigue into a more stable world where tech is driven by the spec, and not by how a framework writer wants the spec to look like... just my two pennies on it :D