Awesome findings thanks for sharing!! I'm curious if you've had a chance to maintain a Preact app for awhile. I always try to start with preact, but in every project that ended up being long-lived I've regretted it.
-
-
Replying to @patrickhulce @PeterssonJesper and
I always end up getting burned by a subtle inconsistency with react or need some integration later on that it doesn't support and end with wasted days that weren't worth the 40k. That effort if invested elsewhere in the app usually could have had bigger perf wins.
1 reply 0 retweets 0 likes -
Replying to @patrickhulce @PeterssonJesper and
How much of this would be fixed by starting w/ Preact, in your experience?
1 reply 0 retweets 2 likes -
Replying to @slightlylate @PeterssonJesper and
These *are* all projects that started with preact. I still think it's valuable to start with and if you never run into its limitations, then great! But thusfar where a very large application was maintained consistently it always seemed to outgrow preact in the end.
1 reply 0 retweets 1 like -
Replying to @patrickhulce @slightlylate and
And for that reason I get worried when we pin hopes for improvement on telling existing large and complicated applications to make the switch from React to Preact. (Not saying that's what's happening here, but it feels like I see this advice often enough to get nervous)
2 replies 0 retweets 1 like -
Replying to @patrickhulce @slightlylate and
Anything you can share? The preact team happily want to make it more consistent
1 reply 0 retweets 1 like -
Replying to @wardpeet @slightlylate and
https://github.com/preactjs/preact-router/issues/333 … is a good example of the type of thing I ran into. It's not like preact is doing anything wrong, or I'm trying to knock it. It just has a (very reasonable) tradeoff of performance over feature set and "just works like React".
1 reply 0 retweets 0 likes -
Replying to @patrickhulce @wardpeet and
And projects that lived long enough I always hit a point where the performance bottlenecks are not really coming from the 40k preact saves me over react, they're coming from my bandwidth to tackle more complicated perf improvements like code splitting, and async UI patterns.
2 replies 0 retweets 1 like -
Replying to @patrickhulce @wardpeet and
Dealing with subtleties like this when you already know React takes time away from focusing on those other improvements is all.
1 reply 0 retweets 0 likes -
Replying to @patrickhulce @wardpeet and
It's also just a lot more fun to tackle the impactful perf work, moving things off main thread, splitting bundles, etc than to research befuddling bugs, so a slightly selfish preference involved there too
1 reply 0 retweets 1 like
-
-
Replying to @slightlylate @wardpeet and
I hope that doesn't mean you'll write off the objective reasons that reach the same conclusion Alex
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.