undefined | Better HN

0 pointsevantbyrne2y ago0 comments

> The dom was a failure, react was a failure. What do you think going back to the DOM will do?

It'll give me that extra 50% effort back. Although I've used React for years, I have never been on the bandwagon. Having built many React SPAs with different teams at this point I'm confident it has always been a step backwards.

0 comments

3 comments · 1 top-level

corethree2y ago· 2 in thread

Yeah but react was designed to address a problem. I don't know if you recall but people were complaining a lot back then. There were tons of frameworks attempting to solve the issue. Only react came out in top.

By stepping back we are just going back to the same problem.

The next abstraction will attempt to solve the same problem again. Very likely in a similar way react failed, the next abstraction will introduce new issues and there will be another trend to go backwards again.

evantbyrneOP2y ago

I don't have fond memories of early React; It was extremely verbose not having hooks until relatively recently, build tools were necessary but a horrible mess, and it was falsely advertised as being faster than vanilla JS. Hype around Facebook carried React. It has improved massively since then, but so has vanilla JS. I don't see a transition away from React as a step back at all. React made rendering new elements client-side and attaching events cleaner, but that was never a hard problem per se and we have web components now.

corethree2y ago

I never said a transition back from react is not an improvement. Again you're not getting it.

I'm saying we had problems with vanilla js initially and we've never moved forward. The fact that we are going back to vanilla js is reopening all the old issues are a sign that we are in stagnation.

Nothing has changed. It's a circle of attempting to improve and failing.

1 more reply

j / k navigate · click thread line to collapse