[sibeliuss]

I hate RSC so much. Most hated technology of them all. And this very helpful / necessary blog post is infuriating, given that not so long ago the entirety of the react stack was capable of being held in one's head. It took very little expertise to make something that worked perfectly fine for most users.

Those days are gone. Scale your Next.js RSC app to anything larger than a toy or marketing site and get f'ing burned.

[alexanderchr]

Just got handed a next app that is currently just beyond toy stage. In what way am I about to get burned? Genuinely curious for opinions

[sibeliuss]

Well, to start with, you'll need to study this dreadful blog post on inspecting RSC activity. And then read this: https://www.comfydeploy.com/blog/you-dont-need-nextjs

Are you using the pages router or the app router? If you're using the pages router you'll probably be fine.

[chamomeal]

I’m not sure if it’s still the case, but I remember people being incensed at next.js’s overly-aggressive caching. Might want to google for those GitHub issues and see if it’s still relevant.

[chamomeal]

Yeah I have to agree. It’s funny Next.js is so convincingly sold to beginner devs as an easier solution than SPA + any backend.

When it works, it really is easy. But when it doesn’t work, it is absolutely infuriating. Too much magic going on, I guess.

A couple months ago, I was still under the impression that next.js is the easiest way to scaffold a simple site. I even tried hosting it on vercel for ultra-easy mode.

I got some inscrutable build errors that had like the thumbs-ups on an unresolved GitHub issue. So I tried running it from a VPS I already had, and it worked fine!

I would absolutely not use it again though. Vite is great, and if I need SSR at any point I’ll just hope that the tanstack SSR solution is 1.0 by then lol