React Won by Default – and It's Killing Front End Innovation

Re:React Won by Default – and It's Killing Front End Innovation by KronisLV on Tuesday September 16, 2025 @01:38AM (#45258412)

See: multi MB downloads to display a few forms in a browser. Software that can’t work well with literal GBs of memory (some of it being a full browser runtime for some desktop forms). Games that run bad thanks to UE5 coming preloaded with footguns that ensure almost every developer will ship games that run poorly. Operating systems that run worse than a decade ago for even the parts that are functionally the same (e.g. a file explorer or start menu).

I sure love the smell of Wirth’s law in the morning - smells like my PC melting.

[ Parent | on HN ]

Re:React Won by Default – and It's Killing Front End Innovation by Banou on Tuesday September 16, 2025 @01:53AM (#45258503)

React in itself isn't that heavy, and things like preact exists if you want an even lighter library, it's mostly other dependencies that are heavy, so the blame is mostly on the side of the devs, not react, for having heavy and clunky software.

[ Parent | on HN ]

Re:React Won by Default – and It's Killing Front End Innovation by tcfhgj on Tuesday September 16, 2025 @03:58AM (#45259345)

https://krausest.github.io/js-framework-benchmark/current.ht...

Select all angular, leptos, vue, solid and react variants -> react literally is consistently the slowest

[ Parent | on HN ]

Re:React Won by Default – and It's Killing Front End Innovation by Banou on Tuesday September 16, 2025 @05:09AM (#45259868)

Good thing that 99% websites don't need to modify 1k dom elements every seconds then, if you do using a DOM library isn't the right choice. My comment was about size library, in response to the parent comment about MBs of js. I'd gladly take a 10ms slower update on 1k rows(that practically never happens, ever heard of virtual lists?) for a maintainable codebase any day.

[ Parent | on HN ]