Abstractions like JSX or other templating languages are a actually commitment to building on top of the standardized APIs, which we have been given no choice but to leverage... *forever*.
Abstractions are fine. The biggest struggle is keeping the cost down.
-
-
Replying to @BenLesh @slightlylate
There's always been this struggle, where the dev masses seem to find huge benefits to abstractions on top of standardized APIs, but the abstractions rarely make it to a standards trajectory. So we're stuck with the hard job of balancing developer ergonomics and app size.
1 reply 0 retweets 17 likes -
Replying to @BenLesh @slightlylate
There's a big disconnect between web developers, web framework developers, browser developers and standards bodies. IMO, none of them, as a group, are really good at understanding the others' struggles because each one of them has a full time job doing their part.
3 replies 10 retweets 83 likes -
Replying to @BenLesh @slightlylate
An overwhelming majority of representatives attending TC39 meetings are web developers, web framework developers, browser developers and runtime implementors. They comprise the technical committee that is responsible for writing the specification that becomes the standard.
1 reply 0 retweets 4 likes -
We worked hard to make that true! Began inviting more framework folks in '10, '11
2 replies 0 retweets 2 likes -
Replying to @slightlylate @rwaldron
It still feels like something is broken at a higher level though. It seems like incentives aren't aligned properly or something. I don't think any one group is to blame.
1 reply 0 retweets 1 like -
And this is all my PERSONAL take on it. I could be dead wrong.
1 reply 0 retweets 0 likes -
Like: Why do we have the same conversations about this over and over? Why are there new frameworks all the time? Why is everyone using one? What are our goals around this? Who's measuring? Maybe all of these questions are asked and answered, and I just lack context.
2 replies 0 retweets 2 likes -
I feel like a part of it is that we had stasis for very long & projects pushed the edges of the platform atop one another, each setting new expectations - there's still a lot of catching up from that and standardization is slow.. maybe.
1 reply 0 retweets 1 like -
It's more complex than that: many browser projects are staffed from OS-funded teams. No OS really wants an internal competitor. Changing what platforms can do requires appetite.
3 replies 0 retweets 3 likes
This plays out in subtle, deadweight-lossy ways.
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.