I 90% just want easy JSON POST.
Comment on Is jQuery still the go-to JS helper library?
Max_P@lemmy.max-p.me 11 months ago
It depends what you want to do and the amount of polyfills/backwards compatibility you need.
Nowadays most projects use one of the big frameworks like React/Vue/Svelte and others which take a vastly different approach to maintaining the DOM and for the most part you never manipulate nodes yourself, therefore you don’t need jQuery and it’s not used much anymore. JSX is weird at first but it’s actually quite nice. Some of those libraries like SolidJS have impressively low overhead.
And for those that like to stick to just minimal JS, the browser APIs have matured a lot so a lot of jQuery isn’t really necessary anymore either. We have querySelectorAll and things like Array.prototype.forEach and Array.prototype.map and arrow functions that cut down a lot on what shortcuts jQuery would offer. Visual effects are usually done with CSS animations and just switching up classes. Everything AJAX is easier and cleaner with the new fetch() function and accessories. Vanilla JavaScript is for the most part quite usable and easy these days. You can even create custom HTML elements from JavaScript to make your life easier!
But if you’re looking at the jQuery API specifically, you can still use jQuery today. It’s still maintained and functional. I think modern versions are pretty small too since it no longer needs half of it to be Internet Explorer hacks and other obsolete browsers that were holding web development back.
magnolia_mayhem@lemmy.world 11 months ago
Max_P@lemmy.max-p.me 11 months ago
Yep, that’s definitely covered: developer.mozilla.org/en-US/docs/…/Using_Fetch#su…
Lord_ToRA@lemmy.world 11 months ago
Yeah, Fetch is so much better than jQuery’s http API, and if you need something more than Fetch, then Axios is far superior.
kameecoding@lemmy.world 11 months ago
JSX is fucking weird compared to vue
realharo@lemm.ee 11 months ago
Custom template language and custom DOM attributes are way weirder than just using language-native constructs (ternary operator, map/filter, variables, etc.) directly like you can in JSX.
kameecoding@lemmy.world 11 months ago
nah mate,mixing html into js is fucked, no matter how hard you cope.
realharo@lemm.ee 11 months ago
Still better than whatever the hell this is
vuejs.org/guide/essentials/template-syntax
The more you scroll down, the worse it gets.
And this too: vuejs.org/guide/essentials/list
spartanatreyu@programming.dev 11 months ago
DOM attributes are built for browsers and frameworks to take advantage of.
The style of some of those frameworks to stick symbols in there is weird. But that only goes against those frameworks. It doesn’t impact how good DOM attributes actually are.
DroneRights@lemm.ee 11 months ago
Vue sucks. A pretty graphic of a CGI robot convincing untrained programmers to merge their web files and produce unreadable garbage as the output file.
CmdrKeen@lemmy.today 11 months ago
Both are weird compared to Svelte.
spartanatreyu@programming.dev 11 months ago
Svelte uses labels, so Svelte itself is weird compared to everything. Except in a way to goto-style control-flow code.
CmdrKeen@lemmy.today 11 months ago
You mean these? Does it use them internally, because I haven’t really seen them in any Svelte code.
If so, what does it matter what the compiler does in order to make your code work, so long as it’s legal? It’s perfectly valid JS, that’s all that counts.
I wouldn’t say Svelte is weird as much as it’s different. That’s the whole point after all. Instead of adding a bunch of library bloat and keeping an entire copy of the DOM to constantly compare to and derive changes from, it compiles your components down to native JS that manipulates the DOM directly, like you would by hand. Except of course the compiler uses different ways to achieve that than you would, but that’s because it doesn’t have to care about readability, as long as it creates valid and efficient code.