… Back when I started, Next.js made server side rendering incredibly easy, but it turns out I didn't need it. My marketing site is entirely static, and my app is entirely client rendered.
Original discussionNext.js is infuriating579 source comments · at importI 100% agree. I've ran into the same issues, and I would never use Next.js for anything, and I will encourage every team at work to use something else. In general Next.js has so many layers of abstraction that 99.9999% of projects don't need. And the ones that do are probably better off building a bespoke solution from lower level parts. Next.js is easily the worst technology I've ever used.
Full originalBring your own experience to the conversation.
I also use next and use the pages router. Makes for a development friendly react front end. And I have some use cases where I want to have a headless crm/api “hidden” behind the front end. So in these cases using next as a backend proxy works well for me.
Full originalI would recommend React Router over Tanstack. I tried both and RR was so much easier and more reliable. Tanstack seems to be following Next.js in that they’re just over complicating everything and their docs felt lacking for the most of their features.
Full originalI regret “upgrading” my personal site to app router. Big mistake esp for is an almost purely static site. Sadly tan stacks releases a new version every other day and react router was complete 5 versions ago but cannot seem to keep changing the api to stay relevant in the never ending js relevancy ending war.
Full originalRespect different perspectives. Share concrete experiences.
Sign in to post, reply, repost, and quote.