undefined | Better HN

0 pointsepolanski7mo ago0 comments

> Being able to render 100k table line updates simultaneously instead of 10k or whatever isn't fundamentally going to make the difference for all of those other requirements.

React's performance are way more severe and ubiquitous and user impacting.

I'd really love to see the websites you're writing in React and lunch a lighthouse or to simulate how do they perform for somebody on a slightly slower connection or not being on the latest iPhone.

Because I know my users include bank clerks or post office cashiers on 10+ year old computers being used at work as much as people on vacation with very poor signal on the beach.

Of course, if you only experience your website from your MBP on cable you thing the issues are only at "10k rows" level.

0 comments

interstice7mo ago

We target <3s to usable on lighthouse mobile, ideally less but I don’t design the sites so only so much I can do about large above fold images etc. the truth is react isn’t that bad compared to latency or other issues on the kind of use case you’re describing

interstice7mo ago

I should clarify - this is headless international ecommerce, so that 3s includes localisation, currency, inventory, cart, video, tracking scripts etc. If you'd like 200ms to live on a static site I can do that too, it's just a bit different.

j / k navigate · click thread line to collapse

0 comments

interstice7mo ago

j / k navigate · click thread line to collapse