At 3kb as opposed to 40kb+ for the basic library as well begin designed around virtual DOM performance in ways that agree with my ideas about our needs. I'm not really an expert on that part of the equation, but the ability to deliver a JavaScript bundle that is so small is extremely appealing. Right now, our entire JavaScript file is 18kb including all libraries and business logic code, and that is without any special effort to be efficient in our actual coding practice.
This doesn't matter as much for a USA-based desktop computer, but inconsistent network conditions depending on locality and device is something I care deeply about and a 13x savings in core library dependencies is a big win IMO.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I have no experience with Preact, but could you elaborate on "way more economical alternative to React" ? Just curious about what problems it solves.
At 3kb as opposed to 40kb+ for the basic library as well begin designed around virtual DOM performance in ways that agree with my ideas about our needs. I'm not really an expert on that part of the equation, but the ability to deliver a JavaScript bundle that is so small is extremely appealing. Right now, our entire JavaScript file is 18kb including all libraries and business logic code, and that is without any special effort to be efficient in our actual coding practice.
This doesn't matter as much for a USA-based desktop computer, but inconsistent network conditions depending on locality and device is something I care deeply about and a 13x savings in core library dependencies is a big win IMO.