Hacker News new | ask | show | jobs
by coolhand2120 919 days ago
As someone who has pissed away thousands of team hours working with the next.js abomination I’m very happy to see Astro take off. I keep thinking “this looks like one of my very first terribly architected, organically created messes”. Astro may not be better, but just statistically speaking you probably aren’t going to be worse. Next is a house of cards. The architecture is as bad as the code base. The only features anyone wants are perpetually in beta. The documentation is probably the only thing worse than the runtime. We dropped SSR and used prerender.io to accomplish SEO and look back at that decision as a great one. I want to try Astro, looks more professional and propose built. Not at all interested in SaaS hosting.
2 comments

Anything specific? We use Next very successfully, and, well it almost became the main way to use React nowadays... pretty good track record for an "abomination". It's not 100% there, I dislike some features built around Vercel offerings (eg. middleware) but it's... a good idea.
Is this specific to Next.js app router? The pages router has been quite good to me, but the app router is something that matches your experience.
As an outsider: what exactly is it about "routers" that justifies so much change? Aren't there plenty of established designs to copy from other stateful UI frameworks?
I think supporting React Server Components is at the core of this issue. A ton of changes were necessary to support RSC and a different router is just one of many things that changed. Important features have been sacrificed to make it happen. You for instance no longer have access to the request/ response object in middleware or layouts. Currently playing with Remix as an alternative.
We are using Remix at work. We are super happy with it. None of the nonsense artificial limitations of Next, great integration with express, and a really simple model which, if you ever used a traditional “MVC” framework, will make you feel right at home.