Right, and our theory going into ES6 development (I co-lead the team that proposed promises/async-await, classes, etc.) was that by upgrading the baseline, we'd be able to remove cruft. Can we mark those beliefs to market and come away happy today?
Yep. What's the prognosis? Does committee grok it already burned through runway and is late to deliver?
-
-
But let's say it works out...what's the case that we will not just continue to pile more transpilation on? What evidence shows meanings reductions in it vs. now fast-moving 90% browser-reach baseline?
-
I want to believe. I have spent a decade mining this vein...but community doesn't want to hear we can't afford profligate ways, and node/server/cli tools are only insulating devs from costs today (not minimizing and/or providing visibility). What drives change in that behaviour?
- 4 more replies
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.
