Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
olback1101278dWhat's so great about jQuery? As a fullstack dev I'd like to know.
Unless you need to support older browsers. Then sure.
heyheni1832778dvue.js is the new jquery
@olback that is all fine and dandy as a student I guess. As a working professional I make solutions from scratch, not frameworks. As such I find it hard to believe that someone never bothered in knowing about jQuery, specially since I would assume that one would encounter it in the wild on an existing project. Which is normally where I find it.
Different areas I guess :D
@inaba he did say it was a simple yet effective solution, which it is. You can either(for example) make an accordion from scratch with a comb of css and js magic or you can just
$('.item').accordion(); or something like that.
Everyone seems to loathe it, but by heavens it really did save some time in a lot of projects and still does.
fuckwit88178dJust today I was working on a project and needed to hide/show content on a mouse click. And jquery saved me some lines of code there :D
grumpyoldaf81878dJQuery is awesome indeed. Don’t let the haters tell you otherwise. It comes in handy in plenty of situations. Saved my ass when I had a deadline hanging over my head.
Fast-Nop1785678djQuery is super awesome. I wanted to add two integers, and luckily, there was a jQuery plugin to save the day.
Please learn some vanilla js first before getting into jquery.
@AleCx04 Yeah but think about what "simple yet effective" actually means. You're actually doing it right by providing an example of why it's simple yet effective. Even tho using jquery ui to show why jquery is good seems a bit silly. Two libraries to do one thing yadda yadda yadda (and doing one thing that you would normally do with your bootstrap/materialize/whatever.)
is also "simple yet effective", and it's not really using any JS or CSS magic at all.
It's like when you hear someone say "well some people are concerned" or "some activists are concerned" or "[generalized group] think" without actually saying who those people are (and it's just like five random people)
@inaba I'm just taking the piss. You're barking up the wrong tree though.
Yes a lot of Jquery devs don't know shit, but I've been using JS for longer then a lot of devRanters have been alive , if I want to cheat and use a Jquery plugin in a site that already uses it... well try stop me 😅
But I wouldn't import Jquery for the sake of "I don't know how JS works".
JQuery is just a giant wrapper, and if that's what people want to use, then so be it.
IntrusionCM71377dIt's simple - JQuery solves a lot of pain points.
Yes. You can do vanilla.
But especially when it comes down to corporate sites, which are not based on any JS framework, it can be very painful.
Checking for ES 5 via eg Modernizr is not enough... There are still a lot of quirks in some browsers.
I'd rather use JQuery than trying to think about getting it to work.
The most hated shit is - especially for corporate pages - sticking / unsticking content, making tables sticky on X and Y axis with fixed headers and so on.
Yes you can throw a bazillion of CSS at it (eg tbody rendering as block and other stuff like this) or you can try to whip up everything in vanilla JS (eg viewport calculations for scroll offset for fixed positions) but believe me. As soon as the client reports that it does not work on <random fucked up browser> you will not be happy.
And especially CSS fuckery can open a wormhole of new bugs.
Just using JQuery is less painful.
Fast-Nop1785676djQuery did solve a lot of pain point back then when it had to paper over the browser incompatibilities. These days are OVER. Welcome to 2019. They have already been over for some YEARS.
jQuery itself doesn't even support old IE anymore from jQuery version 2 on, which is why 85% of all jQuery websites are still on version 1, despite security holes.
These days, jQuery has four main use cases:
1) Legacy projects where nobody wants to pay the cost of the rewrite - so leave shit as is until it has reached its EOL. See the 85%.
2) Things that are as easy and much faster in vanilla JS. Requires knowing vanilla JS, which astonishingly many "devs" don't.
3) Things that should be done in CSS. Requires knowing CSS, which surprisingly many "devs" don't.
4) Things that don't belong on a website anyway (except for artsy demo projects). Like complex animations that can't be done in CSS.
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job