Remix.run Logo
dev_l1x_be 6 hours ago

So React rewrite did not help after all? Imagine, one of the largest software tool companies on Earth cannot reliably REbuild something in React. I lost count of the inconsistency issues React introduced.

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

catigula 6 hours ago | parent [-]

React isn't causing these issues.

dham 3 hours ago | parent | next [-]

Then why is the site slower than it was in 2012 on a 2009 Macbook?

dev_l1x_be 6 hours ago | parent | prev [-]

Good to know. So it only causes the UI inconsistency bugs.

danudey 5 hours ago | parent [-]

The new design/architecture allows them to do great stuff in the name of efficiency; for example, when browsing through some parts of the UI, it's now much more capable of just updating the part of the page that's changed, rather than having to reload the entire thing. This is a significantly better approach for a lot of things.

I understand that the 'updating the part of the page that's changed' functionality is now dramatically slower, more unresponsive, and less reliable than the 'reload the entire thing' approach was, and it feels like browsing the site via Citrix over dial-up half the time, but look, sacrifices have to be made in the name of making things better even if the sacrifice is that things get worse instead.

hunterpayne 4 hours ago | parent [-]

> for example, when browsing through some parts of the UI

React allows this? I didn't realize that I needed React to do this when we used Java and Js to do this 20 years ago. I also didn't realize I needed React to do this when we used Scala and generated Js to do this 10 years ago. JFC, the world didn't start when you turned 18.