I believe there are more options than that. Building a server side rendered app doesn't mean you're "stuck" with jQuery and Bootstrap. You can use any of the modern solutions, be them the mainstream frameworks or tools like Stimulus or Svelte and whatever CSS frameworks you're into.
The main reason to do a SPA, aside from riding trends, is the offline capabilities it gives you.
Building a server side rendered app also doesn't mean you can't have a REST or GraphQL API.
What you call "future proofing" I call "premature optimization" and "complexity brought along by trends". Do you really need a SPA? If the answer is yes, then do it. Otherwise you're perfectly fine without it and your architecture will be simpler to handle.
Reminds me of the microservices vs monolith debate. People saying "well, if you split your app in 10 microservices you can scale them independently". Sure, but you also introduce 10 new problems. Do you need microservices? If yes, go for them, but they are not a better solution in all cases, the same with SPAs. They are great but they have their sets of issues, same for the other options.
I disagree with the equivalence between "old school web apps" and "being held back" nor that we have to move to use SPAs all the time.
They are an alternative, not a replacement or "the better way".
I believe there are more options than that. Building a server side rendered app doesn't mean you're "stuck" with jQuery and Bootstrap. You can use any of the modern solutions, be them the mainstream frameworks or tools like Stimulus or Svelte and whatever CSS frameworks you're into.
The main reason to do a SPA, aside from riding trends, is the offline capabilities it gives you.
Building a server side rendered app also doesn't mean you can't have a REST or GraphQL API.
What you call "future proofing" I call "premature optimization" and "complexity brought along by trends". Do you really need a SPA? If the answer is yes, then do it. Otherwise you're perfectly fine without it and your architecture will be simpler to handle.
Reminds me of the microservices vs monolith debate. People saying "well, if you split your app in 10 microservices you can scale them independently". Sure, but you also introduce 10 new problems. Do you need microservices? If yes, go for them, but they are not a better solution in all cases, the same with SPAs. They are great but they have their sets of issues, same for the other options.
I disagree with the equivalence between "old school web apps" and "being held back" nor that we have to move to use SPAs all the time.
They are an alternative, not a replacement or "the better way".
Insert thank you gif!