excellent news a lot of hypermedia baby was thrown out with the poor-user-experience bathwater when we transitioned from web 1.0 to SPAs, and it's great to see

excellent news a lot of hypermedia baby was thrown out with the poor-user-experience bathwater when we transitioned from web 1.0 to SPAs, and it's great to see hypermedia-oriented libraries making a comeback one aside: I see a lot of either/or thinking around these two options, either you go full SPA or you go full hypermedia. I believe it is more profitable to think in terms of functionality for a given part of your application: sure, if you have a client-state part of your application, maybe a complex reactive library is the right thing. But you probably have a setting page as well, where a hypermedia-oriented solution might be much simpler and just as effective. Why not take the complexity saved there and reallocate it elsewhere in your app?