5 ms·

What's better ? HeadJS [per the link above] - [only a little dev in recent days] LabJS - http://labjs.com/ http://labjs.com/ [seems litte more active dev] Re

by timmyd 15y ago

What's better ? HeadJS [per the link above] - [only a little dev in recent days] LabJS - http://labjs.com/ http://labjs.com/ [seems litte more active dev] RequireJS - http://requirejs.org/ http://requirejs.org/ [most active dev] HeadJS dev seems a little on the light side [ala none - see GitHub for each] ? Anyone have any experience with Lab or Require ?

dave1010uk 15y ago
If all you want is asynchronous JavaScript loading, all you need is the Google Analytics snippet: var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true; ga.src = 'http://www.google-analytics.com/ga.js'; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
threepointone 15y ago
imo (fwiw), stability, a good api, and decent test coverage is a better metric to measure which one's better. I've used LABjs, and it's really good. After a point, I don't _need_ any more dev work done on it.
delambo 15y ago
I can't comment on the dev activity for any of these tools, but I do have experience with lab.js and require.js. From what I have seen, the functionality of head.js looks like a subset of lab.js. Lab.js has a richer API with queueing and waiting. Require.js is a whole different beast - it revolves around the definition of modules (module pattern) and the scripts required to pull down to organize modules. There are a lot of tools in require.js that help with ordering the execution of loaded scripts, pulling down files as text (can't do this in lab.js), and optimizing (compiling modules into one big uglified file). They are all good tools, but different - pick the best one suited for your project.
reustle 15y ago
The creator of LabJS just did a talk at GothamJS and he has essentially devoted his life to making sure it is perfect. I highly recommend taking a good look at it.
johnx123-up 15y ago
Minified of combined files

by timmyd 15y ago

dave1010uk 15y ago

If all you want is asynchronous JavaScript loading, all you need is the Google Analytics snippet: var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true; ga.src = 'http://www.google-analytics.com/ga.js'; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);

threepointone 15y ago

imo (fwiw), stability, a good api, and decent test coverage is a better metric to measure which one's better. I've used LABjs, and it's really good. After a point, I don't _need_ any more dev work done on it.

delambo 15y ago

I can't comment on the dev activity for any of these tools, but I do have experience with lab.js and require.js. From what I have seen, the functionality of head.js looks like a subset of lab.js. Lab.js has a richer API with queueing and waiting. Require.js is a whole different beast - it revolves around the definition of modules (module pattern) and the scripts required to pull down to organize modules. There are a lot of tools in require.js that help with ordering the execution of loaded scripts, pulling down files as text (can't do this in lab.js), and optimizing (compiling modules into one big uglified file). They are all good tools, but different - pick the best one suited for your project.

reustle 15y ago

The creator of LabJS just did a talk at GothamJS and he has essentially devoted his life to making sure it is perfect. I highly recommend taking a good look at it.

johnx123-up 15y ago

Minified of combined files