I'd consider a library to handle i18n in javascript to be extraneous, thus the comment. The current version is 71k before gzipping, which is how you compare it

I'd consider a library to handle i18n in javascript to be extraneous, thus the comment. The current version is 71k before gzipping, which is how you compare it apples-to-apples to everything else that you serve, since everything gets gzipped before it goes out the door and it's easier to compare file sizes on the server than it is to sniff traffic as it goes past. It's a bit dishonest for them to promote it that way on their site. They might as well say it's 0k, since your browser will have it cached. I guess my point is that it's just not useful enough to make up for the bandwidth it takes up. I mean sure, 10 years ago when browsers were genuinely dissimilar, it made sense to abstract out DOM calls. But now, document.getElementById("id").style.width will work exactly the same on every single browser, so all jQuery does is save you a bit of typing. I guess today, all you really need is window.$ = document.getElementById and maybe a home-rolled map function and 50 lines of xmlhttprequest code.