Also React covers more corner cases and in general paves over a much larger part of the Platform than Preact does.
-
-
Replying to @mikesherov @BenLesh and
Any specifics here you can think of?
2 replies 0 retweets 0 likes -
Replying to @matthewcp @BenLesh and
Mike Sherov (he/him) 🚀 Retweeted Sebastian Markbåge
Fun fact: no one really knows, not even the React team. https://twitter.com/sebmarkbage/status/1202098782084780032?s=21 …https://twitter.com/sebmarkbage/status/1202098782084780032 …
Mike Sherov (he/him) 🚀 added,
Sebastian Markbåge @sebmarkbageReplying to @mikesherov @dan_abramovThe truth is, us on the team today, don't understand them all. We're rediscovering them. I've started writing some down as I'm discovering them. Interestingly the oldest features tend to be the worst. Their divergences has settled into de-facto standards.4 replies 0 retweets 0 likes -
Replying to @mikesherov @matthewcp and
That was a general statement. We do know a lot of the edge cases that are documented in our repo by unit tests and in-browser fixtures that can’t be automated. I know Preact doesn’t handle so many of the edge cases just by the code not being there. Curious how much it passes.
1 reply 0 retweets 4 likes -
Replying to @sebmarkbage @mikesherov and
Some cases are easy to argue that the semantics should just be different or should be worked around in user space but everything in there is because someone ran into the problem in a real app.
1 reply 0 retweets 3 likes -
Replying to @sebmarkbage @mikesherov and
Btw I also constantly hear from big companies having trouble switching to Preact because they hit these edge cases when porting an existing app that relies on them being fixed. So I think they do something. However I also believe that if you build the app from the ground up...
3 replies 0 retweets 10 likes -
Replying to @sebmarkbage @mikesherov and
This was us. I love preact, but we did an early experiment to switch, and we saw very little gain. Preact X has come a loooong way so we have to retest at some point. But what makes pages big is not the react core at all, in our observations…
2 replies 1 retweet 21 likes -
Replying to @rauchg @sebmarkbage and
React core takes up about 40% of your mobile JS budget which is not insignificant. But you're right that not curating npm usage is a bigger issue
1 reply 0 retweets 0 likes -
Replying to @matthewcp @sebmarkbage and
Yeah because over the long haul, the React team will either make it smaller, or stable or DCE better However, in practice, the code that any developer pushes or adds to npm tends to balloon unexpectedly out of the blue. Furthermore, Next.js is doing some cool stuff… [cont]
2 replies 0 retweets 1 like -
Replying to @rauchg @sebmarkbage and
There's a cultural issue where Preact libraries tend to be small because the authors are conscious of it and Reacts libraries tend to be big because it's authors are not. This is a major reason to choose Preact, moreso than its own size.
2 replies 0 retweets 6 likes
Preact is the experiment in self-regulation that shows why global limits are necessary
FB culture is toxic here, too.
-
-
Replying to @slightlylate @matthewcp and
Why did you have to add last sentence? This is exactly why you often get attacked.
0 replies 0 retweets 1 likeThanks. 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.