Ignoring @seldo's intemperate, self-owning ad-homenim, let's consider what it might mean...there are many versions! A few:
1.) *literally do exactly this*
2.) add building blocks
3.) start from syntaxhttps://twitter.com/seldo/status/1135150260425318400 …
-
Show this thread
-
Replying to @slightlylate @seldo
To me
@seldo's tweet quite clearly articulates that browsers should ship some form of DOM diffing that can be used as a backend for popular frameworks natively and that JSX should become part of JS.6 replies 0 retweets 17 likes -
I disagree and would feel frustrated if the browser baked DOM diffing directly in. Two reasons: 1. DOM diffing is one of many viable approaches and not very hard to implement 2. React reconciliation is a heuristic (not an algorithm shared in precise details even by vdom folks.)
2 replies 0 retweets 9 likes -
The primitive that is needed is: This is a representation of how I'd like the DOM to look. Please make it so.
3 replies 0 retweets 4 likes -
Replying to @cramforce @wycats and
I think
@dan_abramov himself basically said that the “please make it so” thing you’re describing wouldn’t be useful for React, for a variety of reasons. These proxy discussions about which bits of React should be in DOM do without asking the React themselves seems weird to me.1 reply 0 retweets 1 like -
Replying to @mikesherov @cramforce and
Should be a pretty strong signal that React team is not asking for VDOM or whatever in the browser.
2 replies 0 retweets 2 likes -
Replying to @mikesherov @cramforce and
Every day on jQuery I was asking for more stuff in the browser, because the solutions had a lot of overlap. React has asked for none (except scheduling) because there isn’t as much overlap.
1 reply 0 retweets 2 likes -
Replying to @mikesherov @cramforce and
So then why is your conclusion that the web shouldn't pursue this? The fact that React doesn't overlap as much with the web just means that the web (community) has to pursue this on our own without their direct involvement.
1 reply 0 retweets 1 like -
Replying to @matthewcp @cramforce and
The fact that we *think* we want it is because we see React’s dominance with the idea, and their insight as to why they don’t think it’s better in the browser is *key*. Also, web standards are purposely very slow. What we need in the DOM across all FWs isn’t well understood
2 replies 0 retweets 0 likes
Standards are slow, but platform feature development doesn't have to be as glacial as it has been of late. We can do more; having the frameworks advocate for what they want can help. A commitment to use what's there when it's appropriate shows seriousness.
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.