These are chat archives for systemjs/systemjs

2nd
Apr 2015
Matthew Phillips
@matthewp
Apr 02 2015 16:28
@guybedford are you really going to release a new es6ml using the new half-baked spec?
Seems like a waste of time imo
Guy Bedford
@guybedford
Apr 02 2015 16:30
I know you don't agree with the removal of module names, but i don't think that's reason to call it half-baked
Matthew Phillips
@matthewp
Apr 02 2015 16:31
I mean all of the TODOs written in :)
And a lot of changes haven't been updated
"half-baked" is not an insult, just an acknowledgement that it's very much not done
For example your branch has Loader.prototype.hook even though the discussions now make it sound like that will go away
Guy Bedford
@guybedford
Apr 02 2015 16:35
can you point me to that discussion again?
Matthew Phillips
@matthewp
Apr 02 2015 16:36
No, you'll tell them not to change it since you already implemented :)
Guy Bedford
@guybedford
Apr 02 2015 16:36
I've only got one TODO in the code that really sticks out
Matthew Phillips
@matthewp
Apr 02 2015 16:36
j/k give me a sec
Guy Bedford
@guybedford
Apr 02 2015 16:37
and it's a minor point
Matthew Phillips
@matthewp
Apr 02 2015 16:37
Also, your branch has a window.System even though that doesn't exist and its name is undecided (probably Reflect.loader)
whatwg/loader#35
Guy Bedford
@guybedford
Apr 02 2015 16:38
the loader is a class though
so we can call the global loader something specific
Matthew Phillips
@matthewp
Apr 02 2015 16:39
Reflect.Loader is a class
Reflect.loader is an instance
Guy Bedford
@guybedford
Apr 02 2015 16:39
but I mean System as a subclass
Matthew Phillips
@matthewp
Apr 02 2015 16:39
There is no System in the spec
Guy Bedford
@guybedford
Apr 02 2015 16:39
of course there will be breaking changes
Matthew Phillips
@matthewp
Apr 02 2015 16:39
System is now your thing :)
Guy Bedford
@guybedford
Apr 02 2015 16:39
yes
but it's not as an important distinction anymore now that there will be a contextual loader
that was the primary reason the global needed to be "agreed"
so modules that do dynamic loading had a specified syntax
Matthew Phillips
@matthewp
Apr 02 2015 16:40
what do you mean by "contextual loader" ?
Guy Bedford
@guybedford
Apr 02 2015 16:41
import {loader} from this module;
or something like that
Matthew Phillips
@matthewp
Apr 02 2015 16:41
not following what is different here
what changed?
Guy Bedford
@guybedford
Apr 02 2015 16:42
you no longer use System for dynamic loading in modular code
you use the contextual loader imported from the local context like the code above
even if the global loader was called system that is the cas
that's the important part that needs specifying so that modular code is portable
application code can still use System fine (main entry point)
anyway this is all just talk, I need to get back to code...
Matthew Phillips
@matthewp
Apr 02 2015 16:44
I didn't think the import from this module stuff was specced yet
Looking now... it's another TODO
Matthew Phillips
@matthewp
Apr 02 2015 16:56
What I would do in your shoes is have a long-running spec branch
That tracks the changes
and people who don't mind updating their code often can use that
While still supporting the es6 spec in the master branch, until the new spec is finalized
Otherwise I think people are going to be mad at you when there's a major version bump every month and I don't want that! :)
Guy Bedford
@guybedford
Apr 02 2015 22:16
@matthewp that's exactly what will happen
Matthew Phillips
@matthewp
Apr 02 2015 22:16
people will get mad at you? ;)
Guy Bedford
@guybedford
Apr 02 2015 22:17
I mean having two branches until some form of spec stability is implied
goal is to try and only need 2 - 5 major corrections over the coming years
after the 1.0
Matthew Phillips
@matthewp
Apr 02 2015 22:18
i know, my attempt to lighten things up
Guy Bedford
@guybedford
Apr 02 2015 22:19
sorry so used to having to explain, missed that!
Matthew Phillips
@matthewp
Apr 02 2015 22:20
won't people who are using the caret syntax get breaking changes with 1.0?
^0.18.0 <- will that upgrade me to 1.0.0? can't remember
Guy Bedford
@guybedford
Apr 02 2015 22:23
check it out on http://semver.npmjs.com/
:)
Matthew Phillips
@matthewp
Apr 02 2015 22:25
awesome, didn't know of this tool