4 ms·
> We've got to move past that. No, we've got to move past lazy generalizations. You've boiled down multiple issues to 'people only know jQuery'. Meanwhile the
by allover 9y ago
> We've got to move past that.
No, we've got to move past lazy generalizations.
You've boiled down multiple issues to 'people only know jQuery'. Meanwhile the rest of this thread is dealing with more interesting and accurate specifics.
- beager 9y agoI have not boiled down multiple issues to that, I'm indicating that the problem with jQuery in long-term adoption is that patterns meant to help devs avoid the untenable realm of JS yesterday keep them sheltered from good JS practice today. For that reason, we should move past jquery.
- goatlover 9y ago"We" should do whatever makes sense for the project at hand, be that vanilla, jquery, react, etc. There's a ton of different websites out there. jQuery might be a requirement of the codebase, or already loaded, or heavily used, etc. Or the developer might find it fastest to just drop jquery in for a simple site.