Hacker News Reader

Comment by ls_stats | Hacker News Reader

>Try loading up a library heavy site (i.e. React plus a half dozen associated helpers for state, UI and whatever, which is pretty common) on an old or cheap Android device.

that was the case in 2015 when entry level android devices were quite slow, nowdays a cheap $200 android phone has at least 4-6GB of RAM and an eight core processor.

if that isn't enough for your react powered site, you are doing something very wrong.

View on HN

Multiple times daily I encounter sites that are brutally slow not just on my beefy Android phone, but on my 3GHz+ 8-core 64GB desktop machine.

You need to take performance seriously or it will just be bad. Most of the industry has chosen to be bad.

Well, tracking and advertisement will be doing it, not react.

Keep in mind that React is very single threaded (as is nearly everything in javascript). These phones might have 8 cores; but they tend to have the same single thread performance as 10+ year old iPhones.

That assumes that the bottleneck is JS parsing/execution. The browser itself is not single-threaded and can load/parse resources in parallel.

And I don't buy that most websites would have react as the bottleneck, over the million other js libs, ads and tracking.

No one is asking you to buy it, there is tons of empirical data you can analyze for yourself.

The performance of client-side web applications asymptotically approaches load times of "at most a few hundred milliseconds" on the high end phone models owned by developers.

React sites still feel janky on my 24cores and 48gigs or ram. Which is impressive for all the wrong reasons.

Which react sites? Are you sure you are not a victim of confirmation bias? How often do you check what framework does a smooth and performance website uses?

Because demo sites are snappy on even low-end devices. It's not react itself that causes slowness, but all the other libraries/tracking/ads.

This answers your questions: https://astro.build/blog/2023-web-framework-performance-repo...

Which (correctly) doesn't even have react listed, only frameworks that (may) use react as a library.

So at least be specific what is problematic, is it a particular framework, a particular library, the whole idea behind react (v=f(s)) or what? Anything can be proven against something non-concrete.

Yes.

Reply on news.ycombinator.com