With every major browser supporting WC or about to, frameworks not supporting them are making a choice *against* interop and *for* lockin at this very late date: https://custom-elements-everywhere.com/ https://twitter.com/ElliottZ/status/1134790076599193600 …
-
-
Replying to @slightlylate
Hot take
. Can we give the frameworks a minute? I think support became ubiquitous like a week ago. If it’s still a situation in two years, then sure, but right now tools need to come up with a path where they don’t break their users.1 reply 0 retweets 2 likes -
Replying to @danbucholtz
Everyone seems to have sorted this out with one glaring exception?https://custom-elements-everywhere.com/
4 replies 1 retweet 14 likes -
Replying to @slightlylate @danbucholtz
The main issue with React is that it seems to have a... I'd dare say hatred towards the browser. It's basically a whole VM that's bypassing everything the browser offers to accomodate for the trainwreck that is React Native. All of its faults are a result of that approach.
1 reply 0 retweets 1 like -
It's extremely similar to Java in that regard. Remember "Java everywhere"? Tens of millions of devs jumping on the bandwagon delivering software that makes Electron apps look like they were written by Chris Sawyer in assembly by comparison.
1 reply 0 retweets 1 like -
And then there is react-native-web which is so wrong on so many levels. "Let's write a web app in React Native, so that we can run it through another compatibility layer and then display it on a React VM in the browser."
1 reply 0 retweets 0 likes
I don't think that's generous enough toward RN or RNW; they're significantly better than that. Browsers are also non-"native" compat layers, after all.
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.