It's a really strong selling point that you can use a popular FE framework for all the templates, but at the same time almost completely avoid state management.
> but at the same time almost completely avoid state management
Unless you're just building simple landing pages (I think the context is "web apps" here) or something, you might not have removed any state management, you've just moved it elsewhere.
So the question is, where did you move it instead? The backend?
That is a good point, and I can see that I probably did not communicate what I meant clearly enough.
In my experience most of the state management in FE apps is about fetching and handling data from different types of APIs. With inertia you get a very simple abstraction in that each page gets its own little API. Then inertia takes care of feeding the data from that API to the rendered page when you navigate to it.
For that reason the page can be a "dumb" component, and there really isn't much state to manage.
If the app needs modals, dropdowns, forms e.g., you will need to manage the state of those in the browser, which I think is very reasonable.
Obviously there can also be situations where you'd want to have a small part of the page to fetch some data asynchronously, and for those you'd need to use something else - inertia doesn't do everything.
It's a really strong selling point that you can use a popular FE framework for all the templates, but at the same time almost completely avoid state management.