Hating on {LIBRARY} and telling people they are not real developers because they use {LIBRARY} = never cool, I agree. That said I personally don't see the need for jQuery anymore if it were up to me to decide on the tech stack (barring specific backwards compatibility requirements).
I'm a software developer who writes about Laravel, JavaScript, Rails, Linux, Docker, WordPress and the tech industry. Follow me on Twitter @tylerlwsmith
There's nothing wrong with that. I personally use React for most of my current projects because the kinds of apps I'm building are a bad fit for jQuery.
I think that jQuery has a sweet spot where it's a really good fit: it feels best suited for building interactivity into 5-15 components on an otherwise static site. With less interactivity than that, Vanilla JS may make more sense. When you start having more than 20 interactive components, frameworks like React, Vue and Svelte make a lot of sense.
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.
Hating on
{LIBRARY}and telling people they are not real developers because they use{LIBRARY}= never cool, I agree. That said I personally don't see the need for jQuery anymore if it were up to me to decide on the tech stack (barring specific backwards compatibility requirements).There's nothing wrong with that. I personally use React for most of my current projects because the kinds of apps I'm building are a bad fit for jQuery.
I think that jQuery has a sweet spot where it's a really good fit: it feels best suited for building interactivity into 5-15 components on an otherwise static site. With less interactivity than that, Vanilla JS may make more sense. When you start having more than 20 interactive components, frameworks like React, Vue and Svelte make a lot of sense.