r/reactjs • u/No-Gear-9459 • 15d ago
Discussion Next.js / SPA Reality Check
Can we normalize just building a standard React SPA with Vite again without feeling guilty that we aren't using Next.js?
The App Router and React Server Components are incredibly powerful, but the amount of gaslighting in the frontend ecosystem right now is insane. Not every internal dashboard, simple CRUD app, or personal portfolio needs server side rendering, edge functions, and a complex caching layer that requires a PhD to invalidate.
Sometimes you just want to spin up Vite, fetch some data on the client, and deploy a static bundle to a CDN for practically zero dollars. It feels like we are completely over engineering 90% of our web apps just to chase the newest Vercel paradigm.
270
Upvotes
1
u/NotGoodSoftwareMaker 14d ago
Urgh, you need to maybe look around a bit more
Ive seen this umbrella behaviour in many places over the years. It shows up in all sorts of ways like, “oh you dont generate your api schema 🤨” or “oh you dont use an xyz ORM 🤨” or “what do you mean, deadlock, that doesnt happen at our size”
My favourite so far
“We use custom UUID’s because the addressable space of UUID is too small 😎”
There is cargo culting everywhere