dynamic synchronous import
Jasper St. Pierre
jstpierre at mecheye.net
Sun Sep 28 07:40:33 PDT 2014
I'm confused. We went from bundled, synchronous modules to asynchronous
modules... Why exactly?
And what about the offline case where modules are loaded from disk or are
even complied into an archive file (for fast seek times on rotating disks)?
Are those use cases not important to TC39?
Does the loader API handle all resources? Can I load other assets like
images with it? Can I have one simple preloader for my game which says
map_3 depends on these assets/modules/level scripts, and have ES6 take care
of the rest?
On 28 Sep 2014 07:22, "Sam Tobin-Hochstadt" <samth at cs.indiana.edu> wrote:
> On Sep 28, 2014 1:07 AM, "Domenic Denicola" <domenic at domenicdenicola.com>
> > From: es-discuss [mailto:es-discuss-bounces at mozilla.org] On Behalf Of
> John Lenz
> > > I would like to see some way to preload everything, and be able to
> retrieve them synchronously, something like:
> > Sounds like a good custom loader extension that you could write.
> Note that of all you want is to load of it's already available, and fail
> otherwise, that's already provided. If what you want is sync io though,
> tc39 is not going to add it.
> es-discuss mailing list
> es-discuss at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss