3 ms·
Don't worry, there will be loaders with HTML5. When your application uses a lot of assets, it's pretty much unavoidable, independently of underlying technology
by bd 16y ago
Don't worry, there will be loaders with HTML5.
When your application uses a lot of assets, it's pretty much unavoidable, independently of underlying technology.
In fact, it's probably going to be worse, at least at the beginning, as JS currently lacks a good way to handle packs of binary resources.
Just check Google IO presentation from team that ported Quake 2 to JS [1]. Resource loading was a big pain point, they had to resort to pack data in UTF strings.
http://code.google.com/events/io/2010/sessions/gwt-html5.html http://code.google.com/events/io/2010/sessions/gwt-html5.htm...
- zefhous 16y agoOne thing though, is that browsers cache the data with HTML. Cappuccino uses UTF strings for data, but I wouldn't say "has to resort," it's actually a great experience for both the developer and the user.
- confuzatron 16y agoSilverlight also uses the browser cache. I'm surprised that Flash doesn't make use of it (if I had to guess I'd say it does, or rather at least it can).
- seanalltogether 16y agoFlash has used the browser cache since the inception of the plugin. In fact it routes all http requests through the browser itself, it has no built-in stack of it's own. (unless you're on the desktop)
- confuzatron 16y agoSL uses the browser stack by default, but also lets you use its own HTTP client stack.