HN Explorer

7 comments

[ 0.20 ms ] story [ 23.7 ms ] thread
bretthopper
Great post. Now we just need a rebuttal from Steve Souders.

I wish some of these authors would start collaborating together though. The number of script loaders is getting ridiculous: LABjs, ControlJS, Head JS, and $script.js.

Am I missing any?

busticated
Edited to provide context:

am I missing any (other script loading libs)?

Require js... and it is really nice!

jhrobert
I read that post a few weeks ago, while looking for a script loader. Very interesting indeed.

I fired my editor and coded my own loader (i'm a wheel designer somehow I guess).

I called the result Loadfire http://simpliwiki.com/loadfire.js.html

A funny difference with the other is about the way I deal with dependencies in the asynchronous/evented context of Javascript. Basically: active waits, specified programatically.

The other solutions either ignore the issue and fallback to synchronous like operations or provide some "declarative" ways of specifying the dependencies, but not flexible enough for my needs.

I'm happy with the result (on browsers that supports .async that is).

jpadvo
According to the LABjs homepage, Steve Souders is now working with the author on LABjs.

http://labjs.com/

bretthopper
Steve Souders DID work with the author. Now he made a "competing" script loader called ControlJS which is what this entire blog post is about.
jpadvo
>But ControlJS, HeadJS, and many other script loaders like them are doing the same thing. They aren’t necessarily using the exact same trick as LABjs used, but they are pinning their entire loading functionality on hacky, non-standard behavior.

Well, yikes. I'm using head.js because I figured one loader was just as good as another, but now I'm having second thoughts. Dang, everything is complicated...

yuhong
"I think it’s"

Looks like UTF-8 interpreted as Windows-1252 then converted to UTF-8. And looks like it is happening in quotations of blog comments.