Only working on frontend code occasionally, I found myself wondering why I used jQuery so extensively in the past, and realised it's because most of the features I now consider standard just weren't implemented in JS at all back then
Yeah it's crazy. I picked up JS properly when it had modernised a lot of it's features, and I scoffed a little at the idea of needing to use jQuery before I found out that jQuery was the reason I had a lot of those features to begin with. Just something as simple as querySelector is all thanks to this little library.
@@plugpulled anyone not making a big project loves Jquery for small sample testing sites especially me as a researcher who can't realistically learn all possible frontend tools that keep changing every few days.
I also like how less it needs for work, just 40 KBs both for dev and client... meanwhile Vue install hundreds of NPM packages, easily increasing the project's size over a gigabyte.
It's funny, I was job searching for react/next for a long time. I ended up with a Drupal/PHP job... and a lot of those sites use jquery. So this is actually relevant to me again 😂
Oh wow, someone who uses Drupal. I was forced to work with it last year and just hated it, but there simply was no other devs to work on that and I just had to lol. At least it was a team of 5 😅
jQuery is still awesome! It is the most influential JS framework of all time. When you don’t want hundreds of megabytes from npm and bloated reactive framework du jour AND you don’t want to waste hours learning new tooling du jour AND you just need a little JS help cause it isn’t your primary language then jQuery hits that sweet spot. The fact that it powers so much of the we is a testament to how well it was built.
I still remember JavaScript when jQuery was released. It was a mess and every browser did things differently. And then came jQuery and tried to bring them all on the same track, so that when you wrote code everything behaved at least more or less the same in all browsers without you, the web developer, have to code exceptions for specific browsers (I'm looking at you Internet Explorer 5..) And then JavaScript was upgraded implementing a lot of the features and standards that jQuery already providided. I still stay with jQuery, because for my applications it is enough fast and easy to handle without changes every year. Nevertheless I'm still a bit underwhelmed when it comes to new functions that 4.0 providedes.
I dont understand all the hate JQuery gets. It was and still is an awesome tool, that can do most of the things modern webdevelopment need. Without JQuery we wouldnt probably have things like React, Vue, Svelte and so on. It was the beginning of everything and it was easy to use.
I started using jQuery in 2007, it was such a relief after writing js for netscape and IE 5 and stuff in early 2000s. I quit webdev in 2010; and I am not even your subscriber; but youtube decided to recommend this for me and I very excited of those news! Thanks for sharing.
what do you do these days, if I may ask? Doing webdev since 2000, so I remember IE 5.5 ;) crafting 1 pixel transparent gif images to scale table cols with pixels to create a wireframe for a website layout with tables... 😅 this is stuff only a few remember 😂
I've done my share of jQuery dev. Honestly, it's not all that bad and you can set things up to feel somewhat more "modern" including more or less components (though not as "fancy" as React of course). I don't know, I wouldn't necessarily pick jQuery for a new project, but it's not the worst to use it for legacy projects
@@illegalsmirfhow is vanilla JS verbose? It takes the same number of lines (if not less) to do the same things in JS as jQuery. jQuery is pretty much exclusively used in ancient legacy projects when JS was not as developed.
@@okie9025I mean, just the difference between $('.some-class').click((el)=>el.parentElement.removeChild(el)) vs [...document.querySelectorAll('.some-class')].forEach((el)=>el.addEventListener('click', (el)=>el.parentElement.removeChild(el))) is fairly significant. Granted, you can get that with a simple one liner function, but you asked how vanilla JS is verbose. That is before you even start doing things like selecting a bunch of form elements, setting their values, and displaying the modal. It is certainly less of a slog than previously in Vanilla JS, but there are still things that jQuery just excels at. Would I use it for a new project? no. I have my own micro-library I pull from project to project that makes my workflow easy and effective, but jQuery is no slouch even by modern JS standards.
@@okie9025 document.querySelectorAll(selector).forEach(elm => elm.addEventListener('change', e => console.log(e))) vs $(selector).on('change', e => console.log(e))
jQuery is great for those who want to have dynamic pages, but don't want the headache of fighting full JS frameworks to do anything non cookie cutter. Just straightforward code, you can do whatever you want. Not the best for everything, but it is definitely the easiest solution for many problems.
@@kishirisu1268jQuery lets you do `$("foo")` and have it create a new element to insert wherever you want. Hard to beat that level of stupid-simple element manipulation.
No, jQuery is not great for that. Vanilla JS is. If you are developing a project which doesn't use components, doesn't have multiple distinct submodules within it, or which is made by a solo dev, then there is absolutely no reason to use anything like HTMX or jQuery instead of vanilla JS.
@@NphiniT you can use wp as a framework if you want , and trust me it's a solid one , i used to hate it and then worked with wp for 1 year in a company where i created plugins and other stuff with code yea CODE IN PHP 8 !!! , and some websites were just drag and drop , i think it's like kde "Simple by default, powerful when needed" and it is one of the biggest opensource projects ever created, i use sveltekit and/or django now but still using wp when it's possible
My career has started with jQuery. It's been 4 years I haven't worked on jQuery. Seeing the maintainers put a lot of work into the current release, I feel excited while cherishing fond memories.
It has that distinct smelly/crummy look that other libraries like HTMX do. Definitely focusing on the specific group of web devs who hate their work lol
@@okie9025 smelly/crummy 🤣🤣 It's a very classic look, but only because it's a classic look -- not because it's nice design haha. But it's functional, so I guess "not nice" is just my opinion here
I don't know why hip tech bros dis JQuery. I use it every day and it sure is a timesaver. So much easier than that virtual-dom abstraction BS. Guess I'm just old. :)
At least from my experience it is extremely easy to cause performance problems with jQuery. Back when I was using it in 2016 to develop CRUD applications you could easily run into situations that would just bring the browser entirely to its knees. That and since it is easy to use, it caught on with people who don't program as their primary occupation, so it got a reputation for spaghetti code and callback hell.
I think working with jQuery is like programming in C. You just work on the solution, nothing else. The solutions you make are fast and understandable for other devs. And have less dependencies and are done in less time, compared to using a ''stupid' framework. Dont get me wrong if you build a big JS project you probably will need a framework, because jQuery is just a very powerfull tool.
Bro, you don't have to read paragraphs word for word. We can pause and read if we want. I'm pretty sure you do this to pad the time on your videos. I'm interested in your opinions but it's annoying finding it between all the reading.
People can keep hating on JQuery, to me as a mostly backend focused dev, JQuery felt a lot more understandable and I've done plenty of decent work with it. React on the other hand always felt more complex.
while it is understandable that barely anyone uses them and they add code bloat, it really does suck to drop SO MANY of the slighlty older browsers...like why should a site be completely unable to function merely because I'm using a legacy browser? expected would be that some fancier stuff won't work, but most of the stuff still would...half the point of jquery, instead of other stuff, is incredible compatibility, imho, other than that, there's not all that much reason, unless you know there's specific jquery plugins for stuff you want to use...there's plenty of other nice lightweight libraries...
With HTMX and the whole movement of simpler UI's, imagine if jQuery came back from the dead and dominated once more. I think we all have a soft spot for it.
HTMX is made for people who get confused by vanilla JS, and I think that says a lot. There is absolutely no reason to use HTMX or jQuery when vanilla JS exists. Why do people think they will get made fun of if they use vanilla JS? No, there is absolutely no reason to use HTMX or jQuery if you actually know JS and aren't just a backend dev pretending to call themselves full stack.
@@okie9025 why work hard when you can work smart? You can get ajax and dom manipulation with just one line of htmx, even the line still fits the wordwrap 😂
@@silaspy-ff2ne All for less complexity and more maintainable readable code. At the same time we are balls deep into the age of frameworks for everything that most younger developers coming through rely on them so heavily they don't understand the basics. They can't make good design decisions because they don't have the basics. They find a problem and then look for a package or framework that can solve the problem, rather than using those tools when it's actually beneficial to have a dependency on code maintained by someone else. Then a new thing comes out that a RU-vidr says is great and suddenly it's the new buzz and every starts using it.
I Love your channel. I am not a full-time web-developer (did a lot of backend also), am not even a full-time developer anymore since 3 years. But all frontend stuff I built so far have mostly been pure JS with JQuery, combined with other pure JS libraries. The latest project is now following the same recipe together with Bootstrap 5.3 and everything is ES6 Modules and the build is managed with node and vite. Perfect.
If there were no new frameworks and everybody use jQuery, then world would be more elegant and straightforward. then we don't need to become proficient in every new framework. for instance, if we take React, there are numerous strange patterns and novel theories that contribute needlessly to the massive learning curve. As a result, mastering react takes a lot of time. All of our learning efforts will be in vain when react become obsolete from the industry.
No, your learning won't be in vain. Because new things always build on old things. If something replaces React, it is exceedingly likely that this new framework will incorporate many of the best parts of React.
Unfortunately There's a million plugins out there that will never be updated And so If you are using any of them There's a good chance You can't upgrade
@@genechristiansomoza4931 They hate it because they get told to because they have 0 original thought. The same people will shit on Ruby On Rails for similar daft reasons. Best ignoring these types.
Everything that jQuery does can be done the same way with Vanilla JS. Since for years now. What's the point? These old legacy and Wordpress sites won't update anyway. Probably updating jQuery won't be the biggest problem as other dependencies are causing even more headaches (finding new solutions to abandoned plugins, packages full of security holes) , making it not worth bothering the update, and redo the whole thing instead to pass audit and other security checks. I remember the dark times of crazy DOM manipulation selectors and having to update the HTML manually via code when a variable changes or the hell of lot days of work when you need to do something dynamic and reactive. I don't want to go back to these times, I'll leave jQuery in the past, thanks. They can develop it, I don't care.
always wondered how jQuery was still not updating. Loved using it years and years ago until I caught wind of the new Javascript ES6. Which basically removed jQuery from any project. Really looking forward to this release and seeing how they 'upgrade' the JS experience
As a freelancer I do like JQuery. There are so many good stuff that just works. It's so easy to turn anything JQuery into Wordpress module. I don't care how old libs are as long it's fast to integrate and clients are happy. We all do remember sponsored trends where we should all use backend JS services and where PHP, JQuery and Wordpress are old and obsolete technologies.
jQuery library is just one file, and you can use it directly by just adding it as a script tag, and even just run the html file directly in your browser referencing your own script file. React has a node modules folder deeper than a black hole and you need to compile/transpile and all kinds of shit to make it run. Sorry, there is a reason why many like jQuery or just plain JavaScript. Most of the dom traversion you did in jQuery is ofc easy to do with plain JS now as well so in some sense its not needed anymore.
Can you tell us why you like react more than vue for example? I just started a simple nextjs project, added walletConnect, and i have 1GB of modules... Whenever i make a modification, the waiting time is really bad. Start time of "npm run dev" is terrible. I come from PHP and jquery actually and i liked it. Then i added vuejs instead of jquery, and it was good and fast. Now i do react because of the web3 modules already there, but dev experience is really not nice. Wondering why the hype with "react"
jQuery started my javascript-journey. I suddenly was able to do so much with such ease, compared to how hard stuff was before that. It helped me get used to the syntax and special wierdnesses of js. So... yeah, jquery thaught me javascript.
Funny how most recent front-end devs have probably never touched jQuery. But a lot of us old timers cut our teeth on jQuery because writing Javascript 10 years ago was not very fun. I'm looking forward to trying out v4
jQuery is my all time favourite web library. It's been a life saver ever since it was released. It's just nice. It's what DOM manipulation should've been in the first place.
As an early web developer with a slew of libraries I'd written to handle all sorts of cross-browser inconsistencies and things like modals and DOM manipulation, I was infinitely grateful for jQuery when it first landed, and I always read the release notes whenever an update would hit. I can confidently say jQuery's release notes have always been this comprehensive and well-written.
wdym, not exiting... 12 year old project here with god knows how much jQuery - security audits brings it up every time, slap in that upgrade plugin, run the test suite and lets se where we are. jQuery situation is similar to CoffeeScript, meme as much as you want about it, but remember what we had before it.
I miss the old days when Jquery was king and everyone was super chilled, no arguments over which framework is the best, no comparison over what works and what doesn't. Time flies indeed.
As a backend developer dabbling with frontend, I really liked jQuery, Then everyone started shitting all over it. I couldn't understand why. Ok newer things were good but why turn around and MAKE jQuery bad. TBH since then for me, Frontend devs seem to be more like fashion-conscious ex-Ugg boot wearing pansies that enjoy ridicule over actual usefuleness. WTAF?
why is anyone using that garbage anymore? it seams entirely irrelevant and just a bad dependency if you ask me... the Javascript dom has all you need now days! the fewer dependencies the better if yo ask me!
I had a big gap between my time on Front end applications. When I stopped, jquery was on version 1. New frameworks are largely daunting to get into and (imo) very verbose. I think I managed to skip a full cycle. Server side rendering and jquery are on their way back!
