upvote

points

by CharlieDigital15 hours ago |
comments
upvoteby tacticus14 hours ago|
next
[-]
Was react ever about progress?
reply
upvoteby nine_k10 hours ago|
parent|
[-]
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.

reply
upvoteby nchmy4 hours ago|
parent|
next
[-]
Nah.

https://svelte.dev/blog/virtual-dom-is-pure-overhead

https://news.ycombinator.com/item?id=43971164

reply
upvoteby nine_k1 hours ago|
parent|
[-]
React appeared in 2013, Svelte, in 2016. Three years is a lot. What comes next can see and avoid some pitfalls of earlier designs.
reply
upvoteby youngtaff10 hours ago|
parent|
prev|
[-]
React was a solution to a ten years ago problem
reply
upvoteby youngtaff5 hours ago|
parent|
[-]
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

reply
upvoteby ch_sm4 hours ago|
parent|
[-]
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.
reply
upvoteby agos6 hours ago|
prev|
[-]
if (when?) Signals become a standard, React will be in a tight corner if they decide to ignore them
reply
upvoteby WorldMaker1 hours ago|
parent|
[-]
Not really? `useSignal` is just another hook React needs as a replacement/augment for `useState` and maybe `useEffect`. Signals aren't that special. Arguably that's part of why a lot of people like Signals as a proposal.

(I'm still of the sort that thinks Signals are just worse Observables, so it's not a proposal I'm particularly thrilled about, but were it to be adopted Signals are easy to use in Observable contexts as well, they are just uglier half-implemented BehaviorSubjects, though maybe with a few extra lint rules to prefer Observable behaviors over Signal ones.)

reply