I think it’s all a question of which kind of problems you want to have…
A complex app will have lots of state to manage no matter what. With vanilla JS you’ll have to find a structure for it yourself. Frameworks bring you a structure and a bunch of tradeoffs.
This is basically what I understand about the options out there. I was just holding out some hope that maybe there was something like that.
For me the “old reliable” is react/redux in part due to familiarity, in part cause it solves the problem I value the most - decoupling logic and making it easy to locate where some state update is going wrong.
Something I learned was to not try new tech when building a product I don’t understand yet - and since I spend more time prototyping, I go for the boring stack I’m most productive in.
