[eastbound]

It doesn’t do the internal navigation.

And since React doesn’t have built-in support for pushState (Yes I know React Router, but it really wants a hash router), you really need extra work for an internal router. And therefore, every beginner dev does it manually and slightly inconsistently.

So yes, React is absolutely the driver, same as Java is guilty for Guava existing, because it should have been built-in and perfect.

[tshaddox]

> Yes I know React Router, but it really wants a hash router

This doesn't sound right. The history API has been widely supported by all major browsers (including mobile) since 2013. React was also first released in 2013. Did React Router ever ship a version without a HistoryRouter.

[eastbound]

I have been programming in React for 3 years and never heard of HistoryRouter.

You would be plentiful right to say it’s a programmer’s skills issue. But you have a very stinky pattern of masses of problems of programmers skills issue, leading to 90% React apps breaking the history.

I say it’s React’s fault. It should be built-in.

[dcre]

In this case we are not talking about beginner devs (to their credit, the React docs are pushing people toward frameworks now) — these are literally the developers of a framework, fucking it up in their own docs!