38 ms·

Yeah I get flak when I still use jQuery in new projects. Why do I use it? It fucking works, with no need to depend on npm, the application is a lot snappier tha

Yeah I get flak when I still use jQuery in new projects. Why do I use it? It fucking works, with no need to depend on npm, the application is a lot snappier than using Angular. If I move on from jQuery, it won't be to Angular. I tried React, but I also found it too much boilerplate. I'm trying VueJS next.

spiderfarmer 10y ago
I've noticed that the people that ridicule you for using stuff that works (like jQuery) are the same people that have trouble maintaining their own older code, because they'd much rather just start over.
- xeromal 10y ago
  With JQeury, you can reference one file and get going. With Angular, my frustration has been: * SystemJS - I don't understand what's the problem a lot of the time * TypeScript tsc deciding that Promise is not a known entity. * People telling me not to use SystemJS because it's causing me all my problems. * People telling me not to use Typescript because it's causing all my problems. * Taking 3 days to switch to something not causing my problems. * Technology x causing me another set of problems.
paulddraper 10y ago
> Why do I use it? It fucking works Nowdays that true of vanilla JS. (Didn't use to be.) addEventListener, documentQuerySelector, XMLHttpRequest...yes not everything is a one character function name ($), but it's all quite usuable if you value barebones-no-dependency simplicity.
- arenaninja 10y ago
  I beg to differ... There's still weird Safari/Android bugs from old devices that are out in the wild. Even Windows 8 + IE11 has warts and might be used by application users. I guess it depends on what you're working on, but for us it's expressly not an option to say "we only support the latest version of [insert browser]". Some users aren't even technical enough to differentiate between a browser and the internet
  - paulddraper 10y ago
    What bugs do Safari/Android/IE 11 have that jQuery fixes?

spiderfarmer 10y ago

I've noticed that the people that ridicule you for using stuff that works (like jQuery) are the same people that have trouble maintaining their own older code, because they'd much rather just start over.

xeromal 10y ago
With JQeury, you can reference one file and get going. With Angular, my frustration has been: * SystemJS - I don't understand what's the problem a lot of the time * TypeScript tsc deciding that Promise is not a known entity. * People telling me not to use SystemJS because it's causing me all my problems. * People telling me not to use Typescript because it's causing all my problems. * Taking 3 days to switch to something not causing my problems. * Technology x causing me another set of problems.

paulddraper 10y ago

> Why do I use it? It fucking works Nowdays that true of vanilla JS. (Didn't use to be.) addEventListener, documentQuerySelector, XMLHttpRequest...yes not everything is a one character function name ($), but it's all quite usuable if you value barebones-no-dependency simplicity.

arenaninja 10y ago
I beg to differ... There's still weird Safari/Android bugs from old devices that are out in the wild. Even Windows 8 + IE11 has warts and might be used by application users. I guess it depends on what you're working on, but for us it's expressly not an option to say "we only support the latest version of [insert browser]". Some users aren't even technical enough to differentiate between a browser and the internet
- paulddraper 10y ago
  What bugs do Safari/Android/IE 11 have that jQuery fixes?