I’m in the same boat, SPA feels slower to develop than SSR to me, despite being fairly more experienced in SPA. However, I find it hard to justify choosing SSR

I’m in the same boat, SPA feels slower to develop than SSR to me, despite being fairly more experienced in SPA. However, I find it hard to justify choosing SSR for new projects anymore because: - React makes certain basic things (eg, fetching data, auth) more complex than in SSR, but the overall experience is weirdly addictive and exhilarating at times, especially component reusability on a well set up project. - My clients love it. I am 100% in the camp of “users don’t give a shit how the sausage is made”, but I constantly get praise on how “smooth” the UX feels. I know there are SSR technologies (eg Turbolinks) that can emulate this, but at this point I’m having a hard time justifying learning them properly and risking missing out on that maybe superficial, but addictive, customer praise. - It is indeed what I know best, so what the hell... I believe a competent web developer should know both SPA and SSR and apply what best fits the requirements at hand, but I can also appreciate why devs form biases one way or the other and how this has become a hotly contested topic, and I think we may still be in the same spot in three to five years.