3 ms·
The JavaScript/jQuery community (no difference from outside) was absolutely cancerous. It was impossible to find a javascript question that didn't include top a
by rplnt 9y ago
The JavaScript/jQuery community (no difference from outside) was absolutely cancerous. It was impossible to find a javascript question that didn't include top answer "In jQuery...". Makes my blood boil just thinking about it years later.
I wonder what effect this has on usage. How likely are new developers to use it if virtually every question they have is answered by this (no matter how irrelevant the answer should be today).
- bigmanwalter 9y agoTo be fair, that's because the jQuery solution was usually orders of magnitude simpler. Although newer versions of javascript have absorbed enough of the jQuery api that this is no longer the case.
- rplnt 9y agoAcceptable way would be "Hey, it's done like this, but since the language sucks there's this random library where you can do it this way". Including jQuery for one small task would be stupid. Including jQuery in a non-web project would be weird. Including jQuery in some es variants would be impossible.
- bigmanwalter 9y agoAt that time, javascript was used exclusively for client-side web development. It was pretty much impossible to write ajax requests in any sane fashion that worked cross-browser. It's not such a stretch to assume the user asking the question could use jQuery.
- rplnt 9y agoThe first part is not true. And while I agree with the second, I'm talking about general language questions not related to web in any way (no DOM manipulation, no http requests, etc..).
- dictum 9y agoThe contemporary equivalent, albeit one or a few steps up the abstraction ladder, is "how to get started with (javascript|frontend development)" guides — append "in 2018" for better SEO — which boil down to "use React".