[dimitrisnl]

Oof. I'm sure Vercel might patch this issue. But I had had enough of these little annoyances. For example, the documented way to identify prefetches in the middleware has been broken for weeks (months?).

A lot of small issues that keep adding up. I'm not going to shill something else here, but I have a bit of Next.js fatigue lately. Still love the JS ecosystem though.

Anyway, thanks for bringing this up!

[woutr_be]

I moved away from Next.js, and switched to Astro. Originally I just wanted to go back to basics, but didn't want to bother with having to set up all my routes, templating, serving static assets, build tasks. Astro just handles all that, and it's SSR by default.

I also feel that Astro uses React/Vue as it was intended, as an interactive layer on top of HTML. It also made me realize how little I needed JS frameworks to begin with.

Next just started to feel like to much magic, the server actions felt weird, and just lots of things that required the "NextJS way".

[dimitrisnl]

I tried various astro sites, and as a user, a few things keep bugging me. - Visit their docs https://docs.astro.build/en/basics/astro-pages/ - Click `Routes` in the navigation

Now: 1. There's a flicker in the content where the sidebar moves on the left 2. The title displays `docs.astro.build` for a split second before it says "Routing | Docs"

Especially the second is quite annoying. I see it in every Astro site.

[woutr_be]

That seems to be mostly because of the way they've implemented their docs. It's definitely not something I have with my own sites.

The flicker seems to be because the collapsible nav items are done on the client, and closed by default.

I'm not sure where the title issues are coming from.

[koakuma-chan]

Here is one Astro site https://mayo.clumsy.fish/ with no flickers. Astro is pretty good but after trying RSCs I'm not going back.

[drag0s]

I'm still using Next.js in my work and projects because I still think it may be the best way to ship React to production, but it used to be something fun, enjoyable and productive. sometimes I feel a bit sad about the direction it's going in since the move from pages to the app router.

[dimitrisnl]

The best way to ship React to production is with Vite. It opens up tons of options (Tanstack, RR, Simple SPA, whatever) and you don't even bring the hosting provider into the discussion.

[tisdadd]

This - I spent quite some time fighting the new Next.js conventions not working for me making a legit web app instead of traditional site, switched to vite and was like yay, things work again and so fast. Normally I am all about embracing the framework, but kept thinking for what was happening I could use PHP instead and host anywhere.

[skyeto]

Curious, anything specific that you'd highlight compared to a setup like Remix that make it easier to ship with Next?

[koakuma-chan]

RSC

[dimitrisnl]

Well, they have consistent naming for a start.

[dimitrisnl]

Another follow-up. Some libraries[1] started to break from 15.1.8 onwards, so you had to downgrade to the vulnerable versions the author mentioned as well.

[1]: https://github.com/hashicorp/next-mdx-remote/issues/488

[ekojs]

I share the sentiment. I think we will only be using Next.js for static sites/prebuilt SPA in the future.

[csomar]

Actually Next.js with App router (and with Pages being pushed out) is really bad for SPAs. See this thread: https://github.com/vercel/next.js/discussions/64660

[miyuru]

> I think we will only be using Next.js for static sites/prebuilt SPA in the future.

With whats mentioned in the blog post I would not use it even from static builds.

[Zealotux]

You probably have better alternatives for that: Astro, React Router 7, TanStack.