@domenic @littlecalculist that's how the ES7 process works. We're mopping up legacy bad process now.
-
-
Replying to @wycats
@wycats@littlecalculist If living standard is truly the vision for ES7+ (as it should be) then serious messaging makeover needs to happen.2 replies 0 retweets 0 likes -
Replying to @littlecalculist
@littlecalculist@wycats I am truly surprised you cannot see the impact this has on the dev community and relegate it to "FUD." Step back.1 reply 0 retweets 0 likes -
Replying to @littlecalculist
@littlecalculist@wycats No, I'm saying that they have been burnt enough times I doubt they will trust anymore. "Fool me once..."3 replies 0 retweets 0 likes -
Replying to @domenic
@littlecalculist@wycats They should be made aware nothing is trustable until back-compat in shipping browsers constrains it.2 replies 1 retweet 1 like -
Replying to @littlecalculist
@littlecalculist@wycats That's just untrue. A whole feature, comprehensions, is likely to die even with a shipping browser implementation!3 replies 0 retweets 1 like -
Replying to @domenic2 replies 0 retweets 0 likes
@littlecalculist @domenic step 1. Write spec. Step 2. Implement spec. 3. Feedback and improvement. 4. Implemented in multiple engines.
-
-
Replying to @wycats
@wycats@littlecalculist Now interleave "announce to devs they should write source code using this feature" somewhere in there ;)1 reply 0 retweets 0 likes -
Replying to @domenic
@domenic@littlecalculist yes. That's an important part of the process. Transpilers reduce the abruptness of the risk.0 replies 0 retweets 0 likes
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.