Show HN: Minified.js – a fully-featured, 4K alternative to jQuery and MooTools
1–10 of 145 posts
Re: Show HN: Minified.js – a fully-featured, 4K alternative to jQuery and MooTools
#2Re: Show HN: Minified.js – a fully-featured, 4K alternative to jQuery and MooTools
#3It seems like that would cover most things I would use, however surely there is more to jquery (that I may or may not be using..)
I like that they are including IE6-8, that was a bummer when zepto came out aimed at mobile/modern only
Re: Show HN: Minified.js – a fully-featured, 4K alternative to jQuery and MooTools
#4Re: Show HN: Minified.js – a fully-featured, 4K alternative to jQuery and MooTools
#5Nice work! But it always starts small, then users need a feature here, a feature there next thing you know you have a fat ass library just like the pre-existing ones.
Re: Show HN: Minified.js – a fully-featured, 4K alternative to jQuery and MooTools
#6Probably 4kB more than loading jQuery from cache :)
Re: Show HN: Minified.js – a fully-featured, 4K alternative to jQuery and MooTools
#7Nice work! But it always starts small, then users need a feature here, a feature there next thing you know you have a fat ass library just like the pre-existing ones.
Actually my goal is that the library will always stay under 4kB. Setting yourself a limit is the only way to prevent feature creep, and 4kB seems quite ok. Over time, when support for older browsers can be dropped, there will be space for additional features. I am already working on a second <4kB module though, with support for collections, strings, templates, dates and number/date formatting and parsing. So yes, I k…
Re: Show HN: Minified.js – a fully-featured, 4K alternative to jQuery and MooTools
#8Is this the full comparison? http://minifiedjs.com/#featCmp It seems like that would cover most things I would use, however surely there is more to jquery (that I may or may not be using..) I like that they are including IE6-8, that was a bummer when zepto came out aimed at mobile/modern only
Actually one of the ways I used to decide what features to squeeze in was making a list of all jQuery functions and re-implementing the functionality with Minified. To make sure that I don't miss anything important.
There are some things that are more complicated to do, because you need to work with anonymous functions, but honestly most of them were functions that I had never heard of before and would probably have re-implemented even when using jQuery :)
Re: Show HN: Minified.js – a fully-featured, 4K alternative to jQuery and MooTools
#9Probably 4kB more than loading jQuery from cache :)
Re: Show HN: Minified.js – a fully-featured, 4K alternative to jQuery and MooTools
#10Earlier quoted context omitted.
Actually my goal is that the library will always stay under 4kB. Setting yourself a limit is the only way to prevent feature creep, and 4kB seems quite ok. Over time, when support for older browsers can be dropped, there will be space for additional features. I am already working on a second <4kB module though, with support for collections, strings, templates, dates and number/date formatting and parsing. So yes, I k…
The problem with optimization is that you always have to compromise, either speed, features and performance for size or features and size for speed etc.. I think a probable solution would be to create a dynamically generated framework which allows the user to specify the needed features (jQuery-ui style).