replacing less, sounds good, but it feels that we have to ship more of the new stack, with the eventual end state of "Moving more of the web into JS means that more of the fundamentals must be rebuilt in userland", it's just new fundamentals...
The production web has always been our proving ground. If something is important enough to ship a hack for, it means browsers have more work todo. We cannot evolve through speculation.
-
-
I think that makes sense in some cases. But it seems like it could be biased against developers who will choose an inconvenient but reliable tool over an approximated, hacked together future API for a large-scale site every time. And they may be the ones who need to be heard most
-
Totally agree that we have a pretty bad selection bias problem right now. Injecting data from developer behavior has helped shift us away from smoke-filled-room navel gazing, but shifting the focus to framework authors has similar downsides (self-preservation key among them).
- 1 more reply
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.