ES6 module syntax is changing again: https://gist.github.com/caridy/eefb9b104874465d4e1c … I have no words.
@domenic @littlecalculist that's how the ES7 process works. We're mopping up legacy bad process now.
-
-
@wycats@littlecalculist The real problem here is that modules were presented to devs as "ready to use" in production apps. -
@wycats@littlecalculist People are checking in lots of code into existing repos that is now invalid ES6. And they didn't have any warning. -
@wycats@littlecalculist A strong impression was given that the last round of syntax changes produced a stable, go-live authoring format.
End of conversation
New conversation -
-
-
@wycats@littlecalculist If living standard is truly the vision for ES7+ (as it should be) then serious messaging makeover needs to happen. -
@wycats@littlecalculist E.g. devs should not refer to ES versions; they should be legal Ecma artifacts only that nobody cares about. -
@wycats@littlecalculist Instead devs will care about the same constraints that the committee cares about: implementation compat constraints -
@wycats@littlecalculist Some parts of the document will be frozen because implemented widely; ones with no impls subject to change at will. -
@wycats@littlecalculist Then revs know modules or subclassing are completely up in the air, whereas arrow functions and promises are done. -
@domenic@littlecalculist "completely" cool story bro
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.