Putting HTML, in JS, forever. 
Why!!!???
-
-
We put JS in HTML all the time. The big perf issue is that the parsers can't interop today, so HTML-on-top is most efficient by a country mile. JS-on-top w/o new syntax to integrate other types is going to continue to be slow and memory-inefficient.2 replies 0 retweets 3 likes -
Replying to @slightlylate @wycats and
Putting parsers aside I just don't get what people want to achieve with standardized JSX???
2 replies 0 retweets 1 like -
Replying to @ramlmn @slightlylate and
People want to use JSX without a transpile step. Doesn’t seem weird to me.
1 reply 0 retweets 2 likes -
That’s all fine and good, but JSX is designed in a way that is well integrated into compilers and not designed in a way that could be as easily integrated into the web platform. It’s obvious historically why it was done this way, and likely would not be this popular if it hadn’t
4 replies 0 retweets 5 likes -
Yup, JSX has (currently) a single compile step that translates to functions which run in browser for each load. But standardized it may require a parse and execute phase for each load.
1 reply 0 retweets 1 like -
Is there a good write up of this problem? I don’t understand why it would require re-parsing; Twitter doesn’t seem like the right medium for an explainer.
2 replies 0 retweets 0 likes -
It's probably buried in a comment on a random GitHub issue. Cause that's how we roll.
1 reply 0 retweets 6 likes -
This is I think one of the biggest problems in web standards. There’s all of this stuff that “everybody knows” but there’s nothing you can link to explaining it. It’s in a slide deck. It’s in a github comment that means nothing out of context. It’s in an earlier draft of a spec.
5 replies 1 retweet 0 likes -
Weak references? Everybody knows that you can’t expose GC behavior to the web. ESM? Everybody knows that you can’t be fully compatible cross platform. JSX can’t be standardized. JS’s standard lib must remain small. JS shared memory multithreading is a no go.pic.twitter.com/0p6bOOlarU
4 replies 1 retweet 1 like
In all of those cases, userland and prototype versions died on the fire. In several of them, *I* helped break the logjam. It's unclear to me who you think the argument you're having is with.
-
-
Replying to @slightlylate @polotek and
The fire has burned many things that I wish had survived, but nobody’s writing obituaries for those dead things. So then regular folks are like “hey has anybody asked Goody Osborn what she thinks?!” which wastes everybody’s time.
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.