Better how? They are completely different things made for completely different usecases. It’s like comparing basejumping to hopping on a tranpoline because you’re both technically in the air.
That said, jQuery is most definitely legacy at this point and you can do everything using vanilla js.
yes, vanilla js can do what jquery does, but at the time when i was using it, i found jquery better syntax wise, and there were some pretty cool jquery plugins that required jquery. i am not a frontend developer though.
also, i was talking about many sites using react/angular just for the sake of it, even when there was no real need for using those frameworks. i still see these react sites even now, buggy and less interactive, sometimes not registering interactions properly or crashing.
with jquery, if some javascript breaks, usually that particular functionality stops working, but the rest of the site is still there. with react, especially an SPA, a lot more of the UI depends on the javascript app working properly, so when something goes wrong, you can end up with a much bigger part of the site being broken.
also, with react you generally end up with a whole buildchain. while with jquery you can just load it from a cdn or host it yourself, use it where you need it, and don't use it where you don't. it doesn't really get in the way.
but yes, if your site depends on reactivity a lot, using one of these frontend frameworks is a no brainer. in one of my sites, i am using django and svelte on a few pages where i need to show data more frequently, while the other pages use pure django templates.
also, i was talking about many sites using react/angular just for the sake of it, even when there was no real need for using those frameworks
A lot of people do it because of habit and that they like the paradigm, see how that is starting to look the same as your use of jQuery?
there were some pretty cool jquery plugins that required jquery.
Kind of how there are as many if not more frameworks that depend on react nowadays that people enjoy?
It's also a lot easier to start with a somewhat capable framework and later add things, rather than realizing your project needs react a few years down the road.
sometimes not registering interactions properly or crashing.
This has nothing to do with react, and developers that make broken UIs are just as likely to make broken UIs in any other framework.
with jquery, if some javascript breaks, usually that particular functionality stops working, but the rest of the site is still there. with react, especially an SPA, a lot more of the UI depends on the javascript app working properly, so when something goes wrong, you can end up with a much bigger part of the site being broken.
I'm struggling to picture what you're talking about here. I don't think you fundamentally understand how react works well enough and why this statement makes no sense. What do you mean by broken in this case, and why would react be more broken than vanilla or jQuery?
React is also very opinionated, meaning in theory you should do less mistakes not more.
also, with react you generally end up with a whole buildchain.
This buildchain usually includes things like linting and often TS, things that are great additions to ship less broken code. Again, at least in theory. You also don't have to use JSX/TSX, meaning you can use react form a cdn just the same.
I just find it odd how you defend jQuery so feverously, which objectively has zero use in modern development. But yeah, if you're hosting a couple of static pages with a dropdown menu, who cares what you're using really, but then I don't really know what we're talking about and you definitely don't need jQuery either.
8
u/HerrPotatis 2d ago
Better how? They are completely different things made for completely different usecases. It’s like comparing basejumping to hopping on a tranpoline because you’re both technically in the air.
That said, jQuery is most definitely legacy at this point and you can do everything using vanilla js.