Preact - Performance Optimization by default
A few months ago, I wrote an article based on optimizing react loading time, and most of the reader's...
For further actions, you may consider blocking this person and/or reporting abuse
Then you realize - a lot of components you had don't work with preact, because they were made for react. Then you realize, that you have to implement a lot of functionality that comes out of the box with react... and suddenly you realize why react has a bigger footprint.
And the less code YOU write, the less bugs you have to fix, because let's agree on that - the bigger the codebase the more bugs there are.
Just my .02c
Imagine if there were a standard for components that could work across all the various front-end libs and frameworks.
Oh, there is? custom-elements-everywhere.com/
Of course, React doesn't support them properly.
While I do appreciate what React has given to the community as a whole - it would be so much better if we could get to a point where people are developing web components and then we can just focus on the other libs we need.
Just my .01c (yeah, it's a bargin today)
Yes, if you start a new project you can pick anything. And I wouldn't pick neither React nor Preact - I like Vue better.
But if you are handed a react codebase, converting it to preact isn't a one-day task and the bigger the project the more problems you will meet.
I'm working on the opposite conversion: Preact->React, and our company chose to do so for a reason.
Couldn't have said it better ... look before you leap, things aren't always what they seem, there are always tradeoffs, and in most cases "it depends".
Once we changed experimentally ~2 years ago the codebase to preact and we had decreased pageload times reported both by devtools and analytical tools, even tho evaluation times improved. We reverted. Possibly this improved since then.
However, as it was pointed out, Suspense and Lazy are experimental, React 18 is around the corner with even more features. It simply means preact will be one step behind, no matter what. Not saying it's anyone's fault, everyone can decide on their own which one is more benefitial/important for their project.
There's no such thing as a free lunch ... there are always trade-offs ... performance gains might be marginal and unnoticeable in real world usage ... if it sounds too good to be true, it probably isn't true.
preact-compatis the legacy compat, and isn't used in modern apps. Compat lives in core since v10 (which has been out for 2+ years), see v10/upgrade-guideNext, the comments will be about solidjs
This is great! I always wandered what Preact was about and yout article was very useful! It seems perfect for my current project
Agree. Actually developers/companies who create browsers may eventually sober up and create some useful components and provide better means to validate so we don't have to reinvent the wheel in every framework and component library.
Date input was nearly unusable until a couple of years ago. It still sucks TBH.
Fixed table header was a thing for over a dekade. It still requires a considerable amount ot black magic.
Years ago I was working on a project and at this time chrome lacked the print preview and options dialog. Before developers released this feature, chrome got WebGL, WebSockets and whatnot, but printing was still waiting.
Firefox had an insanely useful plugin jsPrintSetup which no longer works. None of the browsers allows you to do some customizations to the page before printing something (like printing a barcode to a specialized label printer and the rest of the page on you regular one, like we did this with the old version of FF, all this with a single button click)
Recently I was offered to work on a project that was using Telerik's components, which by far are the biggest monstrosity I've ever met and surprisingly to me people are happily using them, and even more surprising to me users are patiently waiting for the page to appear and start working...
I can keep going on and on...
Speed is fine in React.
Thanks for the interesting post.
The performance comparison should also consider the change in performance metrics when the app gets more complex
Performance is not the most important thing.
How about hooks? Can't see those in description.
Yes, hooks exist and work in Preact exactly as you'd expect, see docs
Can you compare it with Svelte now?
Will try it.
I will try this, looking very interesting
Thanks for the post!
Will surely give Preact a try next!