@wycats @littlecalculist Yes, see my timeline. If ES actually presented itself to devs/implementers this way, would be a different story.
-
-
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 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
@domenic @littlecalculist it's not dead. It's getting more work done in true Living Standard style.
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.