ES6 module syntax is changing again: https://gist.github.com/caridy/eefb9b104874465d4e1c … I have no words.
-
-
@wycats@littlecalculist What's ludicrous is that the scope of a feature is still under debate this late in the game. -
@domenic@littlecalculist I thought you consider the concept of "late in the game" ludicrous. By "living document" rules, cutting is fine -
@wycats@littlecalculist Yes, see my timeline. If ES actually presented itself to devs/implementers this way, would be a different story. -
@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 -
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.