Great question!

As a newer school dev I've only ever lived in the world of SPA so I have a pretty biased viewpoint.

But in general it seems that the SPA approach gives us:

• More dynamic UX on the frontend
• Faster rendering times for dynamic elements since it's being done on the client side (but slower for initial renders for some users)
• A more scalable and easier to read codebase (using the component model)

Despite this I dont think SSR is outdated at all and has it's own benefits:

• If search engine optimization is crucial for your project, SSR is often the better choice. Search engines can index server-rendered pages more easily and accurately.
• SSR can provide faster initial page loads, which is important for users with slower internet connections or less powerful devices.
• For sites that don't require complex interactions or frequent updates, SSR with a templating engine can be a lot simpler and more efficient to develop and maintain.
• SSR is more timeless and tested with well-understood patterns and behaviors. This can make development smoother, especially for teams with more experience in traditional web development.

NextJS seems to give some of the best of both worlds for SPA and SSR (and it's what SN is built with!)

Have you played around with Next before?