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 -
Virtual DOM diffing is wasteful and making it native won't change that. It's also entirely unnecessary, and proposals like Template Instantiation achieve the same goals in a much more platform cohesive way.
1 reply 1 retweet 34 likes -
It's also worth noting that we built *tons* of other stuff into the browser that the median React app uses (Promises, Classes, generators, the rest of ES6) and those apps, to near-unit likelihood, still tax users with polyfills for all of them


1 reply 0 retweets 22 likes -
Replying to @slightlylate @justinfagnani and
Find me the FB-sponsored/endorsed React starter kit that doesn't tax 97.5% of users for the benefit of the 2.5% and I'll be more convinced that rising the road up to meet them is a worthy cause:http://gs.statcounter.com/
1 reply 0 retweets 9 likes
Hell, just show me a React-team endorsed path that doesn't polyfill Object.assign, Promises, and Classes *by default* for the 100% of Android users that don't need them (that is, 80% of mobile) and it'll be a new day.
-
-
Replying to @slightlylate @justinfagnani and
I've put my oar into this water for these folks for *so* many years, and the retort is "do more or we won't start down the path of mildly inconveniencing ourselves"?
@seldo, you're smart, would *you* volunteer the careers of your teammates for that cause given the evidence?1 reply 0 retweets 8 likes -
Replying to @slightlylate @justinfagnani and
...or perhaps you mean this in the style of "let's put things into the browser so that folks don't need to pick React"? If so, we've got a lot of 'em to pick from already! Lit, Stencil, Preact, Svelte, etc. etc. Interested teams are spoiled for choice.
2 replies 0 retweets 15 likes - 1 more reply
New conversation -
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.