Regardless, there are hardy folks on our team collaborating to add things that the React team says they want but which we don't expose, e.g. @shubhie's work on scheduling.
Because we serve more than one framework (because option #1 isn't "The Plan"), this needs to be generic.
-
-
Could I beg you to write this up as a blog post? I think the world absolutely needs a canonical answer to, "Why don't you just build React into the browser" that isn't framed by the context of a "you cowards" tweet.
-
Will put it on the backlog.
End of conversation
New conversation -
-
-
ok ok ok but couldn't we just put react in the browser
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
-
Bonjour you can read it here: Thread by
@slightlylate: "Ignoring@seldo's intemperate, self-owning ad-homenim, let's consider what it might mean...there are many versions! A fe […]" https://threadreaderapp.com/thread/1135342338606153729.html … Talk to you soon.
End of conversation
New conversation -
-
-
It'd be interesting if AOT pre-compiled versions of common libraries were "cached" and used if the version matched, but even that sounds like a lot of work, cuz versioning is certainly not consistent between projects. Projects could choose to adapt to comply though.
Thanks. 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.