5 ms·
I think jQuery got a bad rap because so many script kiddies would drop the entire damn framework into a page when they just didn't feel like writing a standard
by FussyZeus 7y ago
I think jQuery got a bad rap because so many script kiddies would drop the entire damn framework into a page when they just didn't feel like writing a standard selector to do a mobile menu.
- chews 7y agofunny, that is the pattern I use, I don't consider it kiddy... it's just efficiant and easy to drop in. le sigh
- FussyZeus 7y agoI mean, if all you're doing is showing and hiding a mobile menu, you can do that in a really expanded form in like 5 lines of vanilla JS, and not have your user download 90 KB* of crap. *And you BETTER be using the minified version for production.
- Roboprog 7y ago90 KB is probably bad for a marketing page, but it’s nothing for a B2B or internal use app, particularly when the second use is just the “you already have it” HTTP header response. Good or bad depending on context.
- johnisgood 7y agoIs bloat sometimes a good thing?
- FussyZeus 7y agoI don't disagree, but when so many public websites are unloading megabytes of Javascript for simple tasks, it feels like that attitude is the core problem. I'm not opposed to using frameworks when they're needed, I just have a problem with people using them to shorten up already short and very easy code because they can't be bothered to Google for a few minutes.