Jason Orendorff

I'm a little confused because the built-in normalize function doesn't throw for URLs, or any other string. (Of course it's possible to override that to do whatever, but if you...

...On the other hand, gensyms might make a nice test case if the GC were to expose a WeakMap primitive. ...On the other other hand, WeakMaps are hard to implement...

I don't expect people to write `System.import('http://some-site.com/app/main.js')` though. Instead: ``` System.import('main', {address: 'http://some-site.com/app/main.js'}) ``` which does not call normalize() or locate() but starts with the fetch() hook. However this does...

@guybedford Hope it's clear what's going on here. We don't expect absolute URLs to be used as module names.

@johnjbarton The name of the module imported by that is `main`, and that's what the Loader uses as the refererName to the normalize hook, if main.js imports other modules. Those...

Yeah, I'm not communicating super well here. Let's start over. You have a collection of modules stored in a directory on a server. You want to load the main module....

@guybedford You can specify the URL through the API, but not through `import` syntax. That's intentional. Modules are libraries; think how weird it is for library source code to contain...

> The scenarios that I am concerned will fail relate to loading two different trees of modules which internally have identical module specifiers. We need to allow these identical module...

> It's possible that the spec has no opinion: you'll take whatever System.normalize() gives, put it back in System.locate() and fetch the result. Right, that's what we do. Is that...

In this use case, `'app/main'` and `'bananas/main'` should work, and that's necessary anyway to get relative module specifiers in app/main.js and bananas/main.js to work. When I said `import('main', ...)` earlier,...