Thanks for the article.

However, there are a few quibbles on my part here.

First, this one: “React came as a happy framework but with many problems and now we are using hundreds of external libraries to fix React” — YouTube comments section.

React is not a framework. It's a library, and it always has been, and that's its advantage. You have to choose from hundreds of external libraries - or use Angular as your Swiss knife instead. So it's not relevant (especially since you're describing yet another external library).

Second, and more importantly, storing data in a URL is a pretty complex solution. I mean you can safely store some secondary local states (modal open/close, dark theme, Español language, current route but this one is silly) but not logical states of the app.

Because of deep links. If you define app state as a URL, you have to consider that users will save it in Favorites as is.

This means that every time you initialize, you need to check the received state - is it up to date and consistent? Is it compatible with the current version of the application? Can we have graceful degradation if not? If it is a shared link - is it allowed for this user? and so on.

Frankly, I'm pretty skeptical that it should be used for anything more complex than a couple of secondary values: it combines the disadvantages of both ephemeral and permanent storage.

But as part of a comprehensive deep links solution - why not, at least it reacts to URL changes and can trigger a state recalculation.