←back to thread

218 points mdhb | 3 comments | | HN request time: 0.773s | source
Show context
pier25 ◴[] No.44392178[source]
The web really needs native templating, reactivity, and data binding.

I can't even begin to imagine how much CPU and bandwidth is wasted with billions of users downloading, parsing, and executing something like React.

replies(4): >>44392500 #>>44393120 #>>44393371 #>>44400323 #
strix_varius ◴[] No.44393120[source]
With the TC39 signals proposal, part of that is making progress.
replies(1): >>44393172 #
CharlieDigital ◴[] No.44393172[source]
Except React.....
replies(2): >>44393456 #>>44395794 #
tacticus ◴[] No.44393456[source]
Was react ever about progress?
replies(1): >>44394351 #
nine_k ◴[] No.44394351[source]
If you valued your sanity when developing complex Web UIs, React was a lifesaver.

DOM sucks though, it's slow, it's heavyweight, it lacks transactions. We're stuck with it, and frameworks like React have to do the DOM diffing + patching thing, explicitly, in JS.

replies(2): >>44394509 #>>44396318 #
1. youngtaff ◴[] No.44394509[source]
React was a solution to a ten years ago problem
replies(1): >>44395972 #
2. youngtaff ◴[] No.44395972[source]
You can downvote it but it doesn’t make it any less true

Alex Russell has written swathes of arguments about Reacts performance issues https://infrequently.org/2024/11/if-not-react-then-what/

The DOM has become much faster since React started over a decade ago, the VDOM really isn’t needed anymore even for app like experiences

React is about developer preference over user experience

replies(1): >>44396325 #
3. ch_sm ◴[] No.44396325[source]
Agree that react isn’t the best implementation of the concept, both in terms of ergonomics and efficiency. But a react-like framework is still very much needed to create complex apps in the browser. So IMHO react is a solution to a very current problem, only not an ideal one.