mvc-router

If the app is MVC-structured you can store global state in the application object. Here's a simple example: https://github.com/edman3d/mvc-router/blob/master/DemoApp/Co... Some frameworks provide session state and cache to store global state. No need for actions, reducers etc.

You do need frameworks, but you don't need big fat frameworks that completely change the programming model and require you to learn its own incantations, rituals and ceremony. React is one such beast. React is only useful if you need to incrementally update complex screens, because simple screens can be re-rendered completely and no one will know the difference. Very few applications need to incrementally update complex screens. If your application doesn't have this need you can use simpler technologies that don't have the same "Care and feed" requirements of React, such as UIBuilder: https://github.com/wisercoder/uibuilder BTW, this lib is a mere 200 lines. Add this 500-line router: https://github.com/edman3d/mvc-router Now you have a usable "framework" that is 700 lines long, super productive, and no incantations, rituals or ceremony.

From hooks documentation: If you look at a typical React application in React DevTools, you will likely find a “wrapper hell” of components surrounded by layers of providers, consumers, higher-order components, render props, and other abstractions. React applications using the MVC model don't have this problem. In MVC Components just handle rendering. Stateful logic go into controllers. I think React is getting unnecessarily complicated because of the "everything is a component" model. I strongly recommend comparing/contrasting this with MVC model. Here's an MVC router that works well with React: https://github.com/edman3d/mvc-router It is a pity that React was originally designed to be the V in MVC, and then the developer community took it in a different direction.