March 29 meeting notes

Claus Reinke claus.reinke at
Fri Mar 30 07:42:06 PDT 2012

> DaveH's presentation about module loaders

Shouldn't any newly designed async loading APIs support promises?
For ES proposals, promises seem to be burried in the concurrency

> DaveH: Imperative module replacement example:
> @websockets exists as version 1.  An implementation wants to improve it to 
> v2:
> import "@websockets" as ws;
> System.set("@websockets", polyfills(ws));

That looks a bit like fiddling with Object.prototype for polyfills. Is that
the recommended approach, and how does it interact with the static
aspects of modules? Wouldn't it be more honest to use conditional
loading, falling back to dynamic module handling?

> Module syntax alternatives:
> module x at "foo.js"
> module x = "foo.js"
> module "foo.js" as x
> module x at "foo.js"

module x from "foo.js"



More information about the es-discuss mailing list