Actually many who did jQuery were proud of it.
Some of us made rock solid sites or improved exiting ones quite a bit using a technology known as progressive enhancement.
Let me tell you what is fragile: the cool things I make today that won't even try to work if I disable Javascript. :-)
Edit: and given what we have seen over the last few days now would be a good time to reconsider if every website really needs to be able to run Javascript.
It's going away because you basically have to write everything twice and it's hell to keep consistent.
Is it just me, or are many of the newer frameworks actually harder to use? I tried Angular 1 about 4 or 5 years ago and it seemed like a complete disaster. Recently, I've been working on Vue and this seems a bit better.
Once your SPA goes through an iteration or two with a few different programmers, you find your events have nasty ordering dependencies and your data becomes inconsistent all on its own. You have no idea why because you can't reproduce any of these issues on your own. You have to watch other people interact with your app just to reproduce bugs ("why the hell would you double click a link?") and git bisect becomes the most productive tool in your toolbox. Most project discussions end with a shrug. You yearn for the days when it was possible for a single human to ever understand the entire app, but that was six months ago and management steadfastly refuses to fund a rewrite. You look wildly around for any sign of hope...
As for Angular, agreed, but I'd rather work with it than a bunch of jQuery. React and Vue are quite pleasant.
Not at all. The issue with an application written in jQuery is a lack of sane state management. Forgetting to initialize (or re-initialize) values, not expecting things to be executed in a different order, and just poor organization in general led to mountains of runtime errors.
Nowadays we use Elm. The difference is night and day. I wrote a post on this topic a few months ago: https://charukiewi.cz/posts/elm/
> Is it just me
Probably.
$('.my-component div').css({ background: 'yellow' })
Array.from(document.querySelectorAll('.my-component div')).map(node => {
node.style.background = 'yellow';
}) document.querySelectorAll('.my-component div').forEach(node => node.style.background = 'yellow');
forEach is much more indicative of what you're actually doing here, which is running through an iterable and mutating properties on each node.
Simple rule of thumb: if you're not using the results of `map`, you shouldn't be using it.
As for simple/readable it’s the same code but s/map/forEach.
Another, bigger factor is that most modern frameworks use some form of templating and binding which means that you have less need to modify/interact with the DOM directly.
The same path is likely on all frameworks - they were designed to solve specific use cases, and as the entire industry matures, different solutions will embed themselves in the industry in different ways, reducing the raison d'etre for each framework, over time.