If you render an <a> in React (or Angular, which I think they're using here), it's just an <a>! You have to do extra work to fuck it up!
But this:
> You have to do extra work to fuck it up!
resonates so hard. I get so angry at people who take extra time out of their day to put so much effort into making things worse. So many things on the internet are fine, but people spend so much on making them worse. Who is this good for? Not me, and likely not the person who wasted their time ruining functional things.
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.
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.
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.
That is news to me that Google is using Nextjs for anything.