4 ms·
if you use regular html, the developer does not need to implement those things
by spencerchubb 3y ago
if you use regular html, the developer does not need to implement those things
- Klonoar 3y agoTheir point is that it’s the dev choosing to do this stuff. Even if using regular HTML/CSS many devs opt to do that stuff.
- michaelmior 3y agoI don't think it's always that the dev is choosing to implement these quirks. They're choosing to add extra functionality, but not always implementing it well. You can choose to have higher latency for the initial request and just display static HTML. Or if you want to load content on demand, then you do have to deal with what happens before anything loads, but I don't think that's the fault of React. Any framework which does this is going to have the same problem that needs to be solved. Similarly to React "breaking" the back button. If you want user interaction without another page load, you have to deal with the consequences such as needing to track page history more explicitly than you might have otherwise. But that's because the dev chose to change the page content without moving to a new URL, not because that was implemented using React.