It has now become a norm that everyone just drops in jQuery and bootstrap css for most of their projects while they might just be needing a DOM handler and a few utility functions. I have nothing against jQuery or Bootstrap. They are awesome to get things rolling but in most cases there is no necessity to load huge JS libraries with lots of utility functions which one might not be using. Not to leave aside the fact that a few third party analytics, tracking, help desk tools also load/include jQuery in their bloated script.
MicroJS is a good resource. I am wondering how many of the frameworks listed there are actively developed/maintained. Adding the last commit date information might be super useful.
> there is no necessity to load huge JS libraries with lots of utility functions which one might not be using.
I think we really need to see a tracing link-time-optimizer for Javascript code that can be run as part of an asset pipeline. Dump in your huge JS library, run your client scripts (with a thorough test suite) to detect what functions of the big library are or aren't called, then cull off the functions that aren't when writing out the final "compiled-and-linked" client library.
Considering jQuery is available on Google's CDN, and lots of websites just fetch it from there, it's not necessarily true that using a smaller library will actually translate into slower load times in most cases. Similarly, if you concatenate all your javascript together, that gets rid of the main culprit where slow page loads are concerned, which is latency, not file size.
I started using zepto recently, it's at 7.4k min+gziped, not the 3.3 listed on this site. Still a super useful site, it might just be slightly out of date.
Very cool! I'd very much like to be able to sort by popularity, so when I'm trying to find an off-the-shelf library for something I have a general sense of what has support in the community.
Since the list is so long, an "about" link on top of the page to link to the bottom would be helpful (eg. I want to find out what constitues as a "micro" framework - currently it's 5k).
It would be nice if I could use a minifying compiler that would strip what I don't use from JQuery, without having to also organize my JS source in a compileable form.
[+] [-] ramanujam|14 years ago|reply
MicroJS is a good resource. I am wondering how many of the frameworks listed there are actively developed/maintained. Adding the last commit date information might be super useful.
[+] [-] derefr|14 years ago|reply
I think we really need to see a tracing link-time-optimizer for Javascript code that can be run as part of an asset pipeline. Dump in your huge JS library, run your client scripts (with a thorough test suite) to detect what functions of the big library are or aren't called, then cull off the functions that aren't when writing out the final "compiled-and-linked" client library.
[+] [-] stdbrouw|14 years ago|reply
[+] [-] latch|14 years ago|reply
[+] [-] madrobby|14 years ago|reply
Zepto's size includes only the core library, not additions like Ajax, Touch and so on, that's where the 3.3k number is coming from.
[+] [-] AlexeyMK|14 years ago|reply
I've put together a pull request which aims to accomplish this goal at https://github.com/madrobby/microjs.com/pull/232.
[+] [-] fuzzythinker|14 years ago|reply
[+] [-] sad_panda|14 years ago|reply
[+] [-] 97s|14 years ago|reply
[+] [-] wahnfrieden|14 years ago|reply
[+] [-] mhansen|14 years ago|reply
[+] [-] martindale|14 years ago|reply
[+] [-] elchief|14 years ago|reply
[+] [-] handzhiev|14 years ago|reply
[+] [-] z0ot|14 years ago|reply