If you’re a front end dev who wants to look important, making the entire application reliant on your fragile client side code can give a lot of hutzpah to your resume.
Backend devs do this as well. You could just as easily start a thread called "Why use MicroServices/Serverless/Kubernetes/NoSQL etc.". Just like SPAs, those things all have a time and a place but unfortunately devs often push for them to be used in order to practice resume-driven-development and so they can play with the shiny new toy that everybody is talking about.
Personally I think SPAs have a time and a place - highly interactive web apps like google docs, facebook, slack etc. should definitely be SPAs. But using React to create a blog site is just ridiculous. Indiehackers.com is a perfect example of a site which would be so much better if it was a plain old statically rendered site. I remember a podcast where the founder of indiehackers said that he used React to build the site because he wasn't happy that the indiehackers business is not technical enough - so using react was a way making it more "techy" even though it actually makes the site worse (he didn't admit that part though). And thats fine for him as he is a solo-entrepreneur, but when developers working on teams take on that mentality it be extremely frustrating for the developers who would rather produce value than produce overly-complicated solutions in order to gain bragging rights.
Comments
The #1 use for an SPA is called “resume padding”.
If you’re a front end dev who wants to look important, making the entire application reliant on your fragile client side code can give a lot of hutzpah to your resume.
Here we go again with the front end developer hate
Backend devs do this as well. You could just as easily start a thread called "Why use MicroServices/Serverless/Kubernetes/NoSQL etc.". Just like SPAs, those things all have a time and a place but unfortunately devs often push for them to be used in order to practice resume-driven-development and so they can play with the shiny new toy that everybody is talking about.
Personally I think SPAs have a time and a place - highly interactive web apps like google docs, facebook, slack etc. should definitely be SPAs. But using React to create a blog site is just ridiculous. Indiehackers.com is a perfect example of a site which would be so much better if it was a plain old statically rendered site. I remember a podcast where the founder of indiehackers said that he used React to build the site because he wasn't happy that the indiehackers business is not technical enough - so using react was a way making it more "techy" even though it actually makes the site worse (he didn't admit that part though). And thats fine for him as he is a solo-entrepreneur, but when developers working on teams take on that mentality it be extremely frustrating for the developers who would rather produce value than produce overly-complicated solutions in order to gain bragging rights.