4 ms·

Is React rendering performance really a pain point worth solving? I've never thought to myself "man I wish React would render faster"... It doesn't seem like th

by a13n 4y ago

Is React rendering performance really a pain point worth solving? I've never thought to myself "man I wish React would render faster"... It doesn't seem like this is whatsoever a bottleneck for our application (~1k unique components). I feel like the main pain point with React is that routing, bundling, SSR, state management, etc. have to be painfully stapled together, and this is what frameworks like Next.js solve for.

deleted 4y ago
[deleted]
- lsalvatore 4y ago
azeirah 4y ago
Don't think it's a pain point, but better performance without feeling a difference (ie not using bubble sort for sorting but using quicksort) is just.. always nice?
smolder 4y ago
How often are you testing on low end devices like say 5 year old budget tablets or netbooks? Speed also correlates with energy use. Does using your site drain batteries faster than it needs to? I find these things often aren't given appropriate consideration, although speed improvements could easily be negligible for your app and its users.
jimmySixDOF 4y ago
Maybe with something like React-Three-Fiber where the frame rates can be 11ms
aporetics 4y ago
Well, let’s look at it from a different angle; not the angle of the user or the developer, but as a matter of computational work and the energy consumed by that work. In a single application or even the life of an application all it might be negligible. But when does it not become negligible? What if react adopted the change and every react app What about for every react app in use suddenly used a fraction less computational power each render? And is it just a monetary cost? Yes, if energy use is your primary concern there are easier ways to reduce it. But in the above context it seems clear that you should take your gains where you can get them.
brundolf 4y ago
It's not usually a problem, but if you're making an app that shows really large amounts of data it can become a bottleneck (I've run into this personally). It also has less to do with number of unique components and more to do with the number of components on the screen at once, and the number that have to be (or end up) re-rendered on each update
Existenceblinks 4y ago
Bloat and slow is really a problem when it comes to GUI app. Slowness means less responsive ui, longer to load is also negative in human's perception. Things get in a way of solving business problem.

by a13n 4y ago

deleted 4y ago

[deleted]

lsalvatore 4y ago

azeirah 4y ago

Don't think it's a pain point, but better performance without feeling a difference (ie not using bubble sort for sorting but using quicksort) is just.. always nice?

smolder 4y ago

How often are you testing on low end devices like say 5 year old budget tablets or netbooks? Speed also correlates with energy use. Does using your site drain batteries faster than it needs to? I find these things often aren't given appropriate consideration, although speed improvements could easily be negligible for your app and its users.

jimmySixDOF 4y ago

Maybe with something like React-Three-Fiber where the frame rates can be 11ms

aporetics 4y ago

Well, let’s look at it from a different angle; not the angle of the user or the developer, but as a matter of computational work and the energy consumed by that work. In a single application or even the life of an application all it might be negligible. But when does it not become negligible? What if react adopted the change and every react app What about for every react app in use suddenly used a fraction less computational power each render? And is it just a monetary cost? Yes, if energy use is your primary concern there are easier ways to reduce it. But in the above context it seems clear that you should take your gains where you can get them.

brundolf 4y ago

It's not usually a problem, but if you're making an app that shows really large amounts of data it can become a bottleneck (I've run into this personally). It also has less to do with number of unique components and more to do with the number of components on the screen at once, and the number that have to be (or end up) re-rendered on each update

Existenceblinks 4y ago

Bloat and slow is really a problem when it comes to GUI app. Slowness means less responsive ui, longer to load is also negative in human's perception. Things get in a way of solving business problem.