Well, I'm a good learner. Me too... But that depends it it's gzipped or not.
I hate seeing js file sizes over 25k, but that's just me.
Wedge automatically caches and gzips all CSS and JS files. It's a feature I spent a lot of time working on, it's working perfectly in all browsers and it really saves a lot of bandwidth if your server doesn't let you enable gzipping automatically on files. (Plus, you save the processing time for gzipping files in the first place, as they're only gzipped once and then cached, as opposed to gzipped on the fly each time the file is requested in SMF for instance.)
The main script file (script.js+theme.js) is 28kb in Wedge (compared to 50kb in SMF for the same data), and gzipped to 10kb, meaning script.js+theme.js+jQuery = 37kb in Wedge, compared to the original 50kb (uncompressed) in SMF. All in all, if your server doesn't support automatic gzipping, then you actually save 13kb of bandwidth per user per session, *and* they get jQuery in the process. (Plus, since you can load jQ externally, you really save a whopping 40kb and an unneeded extra hit :))
I'm not fond of Mootools either. Or Yahoo's solution, for that matter. jQuery is best, but it still has the problem of bloat over time. Sometimes, smaller is better, really. Even switching to Google Closure then to UglifyJS didn't save the library from getting bigger.
If your capable of writing your own, that will work best, it's just more time and bug tracking involved. User's can still add jQuery manually, that's the route I would take. I see no point than have both. But I am a fan of jQuery, and can't stand Mootools...
Yeah... Mainly because many businesses are still running Win2k, where IE6 is the last available version. (Of course, they could use modern browsers that work even on Windows 98, but...)
As far as IE6 goes, it's good to hear it won't be babied like SMF does. People need to upgrade. Most of the current IE6 users are from businesses anyway.
Posted: March 28th, 2011, 07:15 PM