@wycats You tell me.
-
-
Replying to @littlecalculist
@littlecalculist@wycats Sure, modules give no new expressive power in general over ES5 (as evidenced by transpiler); this is not news.2 replies 0 retweets 0 likes -
Replying to @domenic
@domenic@littlecalculist it'sludicrous to consider a strict reduction in scope of an unimplemented feature proof of out of control process1 reply 1 retweet 3 likes -
Replying to @wycats
@wycats@littlecalculist What's ludicrous is that the scope of a feature is still under debate this late in the game.3 replies 0 retweets 0 likes -
Replying to @domenic
@domenic@littlecalculist I thought you consider the concept of "late in the game" ludicrous. By "living document" rules, cutting is fine1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@littlecalculist Yes, see my timeline. If ES actually presented itself to devs/implementers this way, would be a different story.1 reply 0 retweets 0 likes -
Replying to @domenic
@domenic@littlecalculist that's how the ES7 process works. We're mopping up legacy bad process now.2 replies 0 retweets 0 likes -
Replying to @wycats
@wycats@littlecalculist The real problem here is that modules were presented to devs as "ready to use" in production apps.1 reply 0 retweets 0 likes -
Replying to @domenic
@wycats@littlecalculist People are checking in lots of code into existing repos that is now invalid ES6. And they didn't have any warning.2 replies 0 retweets 0 likes
@domenic @littlecalculist transpilers are the impls. They can provide a transition path.
-
-
Replying to @wycats
@wycats@domenic@littlecalculist ejs isn't a transpiler...0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.