Module naming and declarations

Kevin Smith zenparsing at
Tue May 7 13:31:17 PDT 2013

> The whole point of my original email to Andreas is that this doesn't
> work.  These names are *not* intended to specify where to find the
> resource.  They *are* intended to be names that different modules can
> coordinate with.  Should backbone put `import "/js/jquery.js"` in
> their source file?
I think we all understand the problem that you're trying to solve here, but
aren't you putting the cart before the horse?  Can we not design the module
system first, and then layer packages on top?  Do you not agree that that
would be a more robust approach?

{ Kevin }
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the es-discuss mailing list