One year with Next.js App Router and why we're moving on

General Developer Forum In The News
1

As I’ve been using Next.js professionally on my employer’s web app, I find the core design of their App Router and React Server Components (RSC) to be extremely frustrating. And it’s not small bugs or that the API is confusing, but large disagreements about the fundamental design decisions that Vercel and the React team made when building it.

The more webdev events I go to, the more I see people who dislike Next.js, but still get stuck using it. By the end of this article, I will share how me and my colleagues escaped this hell, seamlessly migrating our entire frontend to TanStack Start.

Read in full here:

1 Like
2

Lengthy article, but valid points. Next.js is a minefield. Bought a book on it 3 years ago, and by the time I got to reading it, everything had already changed.

I now have my eye on Svelte, and if I have to deal with React, then Remix is a better alternative.
Vercel is just one hell of a crazy company in my view. So for now, I’ll keep my distance.

1 Like
3

Might be worth checking out hologram as well :icon_biggrin:

1 Like
4

I can’t wait TanStack Start to be v1!

1 Like
5

Interesting, thanks @AstonJ, checked it out. Seems like a relief compared to the way Phoenix/LiveView has been moving with integrated Tailwind CSS. On my watchlist :slight_smile:

1 Like
6

You can use Phoenix without Tailwind mind, lots of people do:

7

I’m drifting off topic, but I get the sense you’re not a fan of Tailwind. What parts of it don’t you like?

1 Like
8

Thanks for the post. A lot of divided opinions and many alternatives but the consesus is that Tailwind is just unnecessary bloat. Sadly, I don’t think it will be easy to convince Chris McCord to drop Tailwind :frowning:

1 Like