BUILD REACT INTO THE BROWSER YOU COWARDS
-
-
Replying to @seldo
I remember that call with prototypejs. And later with jquery. And later with ______
3 replies 1 retweet 37 likes -
Replying to @sroussey
We built browser APIs based on both of those technologies.
1 reply 0 retweets 32 likes -
Replying to @seldo
That wasn’t the call though. People wanted $() for example. They didn’t want partial versions. BTW: $() was a pain when copied from firebug. One returned an element, one returned a stack.
1 reply 0 retweets 6 likes -
Replying to @sroussey
My real position is that there are some stable features within React and common to the other frameworks and we should be looking at promoting them to web APIs. This would allow all the frameworks to get smaller and the web to get faster.
6 replies 11 retweets 82 likes -
Replying to @seldo
Same argument for jquery (smaller and faster web pages). Jquery had far higher adoption. I’d say only 10% knew $ returned a stack.
It also means the apis can’t change.
There is work on built in modules though (KV storage, for example). What react stuff do you propose?1 reply 0 retweets 5 likes -
Replying to @sroussey
I'm not an expert, but all the frameworks do virtual DOM diffing so making it faster by making it native seems like an obvious win.
7 replies 0 retweets 14 likes -
Native is not a magic "be faster" button. O(n) algorithms are still slow, no matter if they're in C++ or JS.
2 replies 1 retweet 36 likes
...and the fastest reactive frameworks aren't doing straight diffing anyway, because it's slow and slow is bad.
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.