Head JS
Out of context: Reply #3
- Started
- Last post
- 4 Responses
- chow0
I don't know if I like head.js, I already use other libraries that provide the same functionality. However, I still disagree with some of the points raised above.
1. Perception is everything. Users do not care how many HTTP requests are required to load a page, they care that the page was usable quickly. This can be improved using non-blocking and parallel JS loading, which head.js claims to provide.
2. If your page relies on DOM ready, you can get there faster by loading your JS in parallel. Of course a better way to improve things is to not rely solely on DOM ready.
3. CSS browser targeting via JS is very useful, and does not imply that more than one style sheet is required, in fact being able to put styles for different target devices in the same sheet is the main benefit. Like say adding some iPad-specific declarations without having to load a separate sheet for iPad. If you think this is useless, perhaps it's because you have never developed something requiring this level of sophistication :)
@Hue, if all you need is browser-specific CSS, check out https://github.com/rafaelp/css_b…