3 ms·
jQuery 2 can fuck off. In fact jQuery as a whole can fuck off. It's been a disasterous slog using it for us. No end of problems with it and associated half-arse
by meaty 14y ago
jQuery 2 can fuck off. In fact jQuery as a whole can fuck off. It's been a disasterous slog using it for us. No end of problems with it and associated half-arsed shitty plugins to the point we've developed our own internal JS API and toolkit which we can control. Even minor version upgrades of jQuery have been dependency hell (we have 110kloc of JS excluding jQuery plugins - a lot!).
We deploy desktop apps (via ClickOnce / direct) as well as web applications, so we're supposedly in the same mire, however they still "just work". They don't suddenly stop working one day. Youre entire toolchain is fine. Just keep it in a VM.
We only just killed a desktop app deployed on Windows NT4 which was thrown together with VC++ 6. I have the VM running now as I'm porting it to .Net 4 (C# this time).
- andybak 14y ago> to the point we've developed our own internal JS API and toolkit which we can control I would have thought submitting a bug fix to jQuery might have been less work.
- meaty 14y agoHarder than it looks. Submitted 20+ bug reports, got 1 solved. jQuery's issue tracking and source management was a baron land of incompetence. By that time we had our own wrapper API that fixed all the jQuery bugs so we just took the guts out and replaced then with our own.