I wonder what problems they are solving. I've found using the native DOM api much more efficient and easier to maintain than using jQuery. Also I think React has exposed a new document model api so I can't imagine there is any use for jQuery in React.
There really isn't any use for it but people stick to what they know. In this case it was about Bootstrap functionality being called from React components using jQuery instead of the React Bootstrap packages.
"There really isn't any use for it but people stick to what they know"
This, and only this is the explanation of people using Jquery now days. (okay there are also some occasional "it makes it easier for me to support IE" situations, but still...)
"I don't think jQuery is every fully going to disappear"
Well, there are still COBAL jobs around. And Jquery was literally used in 90+% of EVERYTHING on the web for a long time. So it will stick around for a very, very long time. (Combined with the fact that some developers will keep using it because "$() is so much less work than document.querySelector()" )
I've personally been in the dev world for a very short amount of time. And I've already met several developers who, ultimately, are pretty darn good devs, but still can't make a web page without Jquery. They just haven't been able to adapt. I never want to be that person...
(Those same devs also tend to suck at modern CSS, like display: flex/grid for layout stuff, and HAVE to use bootstrap...)
Nothing is "wrong" with Jquery. But I literally write vanilla JS faster than Jquery (because I don't use Jquery, so I always have to refer to the docs more often.) Modern JS isn't hard. If somebody has to use Jquery because they can't write vanilla JS they are holding themselves back. So for me, an extra 200kb of dead weight I don't use, would bother me.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I've worked with people who used jQuery to solve ReactJS problems. I don't think jQuery is every fully going to disappear.
I wonder what problems they are solving. I've found using the native DOM api much more efficient and easier to maintain than using jQuery. Also I think React has exposed a new document model api so I can't imagine there is any use for jQuery in React.
There really isn't any use for it but people stick to what they know. In this case it was about Bootstrap functionality being called from React components using jQuery instead of the React Bootstrap packages.
This, and only this is the explanation of people using Jquery now days. (okay there are also some occasional "it makes it easier for me to support IE" situations, but still...)
Well, there are still COBAL jobs around. And Jquery was literally used in 90+% of EVERYTHING on the web for a long time. So it will stick around for a very, very long time. (Combined with the fact that some developers will keep using it because "$() is so much less work than document.querySelector()" )
I've personally been in the dev world for a very short amount of time. And I've already met several developers who, ultimately, are pretty darn good devs, but still can't make a web page without Jquery. They just haven't been able to adapt. I never want to be that person...
(Those same devs also tend to suck at modern CSS, like display: flex/grid for layout stuff, and HAVE to use bootstrap...)
I missed that boat...
Be glad, it was not a great time for frontend development
What is wrong with Jquery? An extra 200kb never killed any page no?
Nothing is "wrong" with Jquery. But I literally write vanilla JS faster than Jquery (because I don't use Jquery, so I always have to refer to the docs more often.) Modern JS isn't hard. If somebody has to use Jquery because they can't write vanilla JS they are holding themselves back. So for me, an extra 200kb of dead weight I don't use, would bother me.