31–38 of 38 posts
I was a happy Netlify user for years until they silently took down my app without warning. They blocked my account based on a bogus DMCA claim, the details of which point to a DIFFERENT app with a similar name. Unacceptable behavior from a hosting provider. I'll never use them again.
Is that other app still up?
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…
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…
Thought experiment: assume the worst: next.js + eleventy is in decline; what does it change in the short-term? It is likely that people using those frameworks are getting things done in them. To me, the fact this whole discussion is happening illustrates how fickle devs are in this particular ecosystem. It's like nobody wants to be caught dead using something that might not be the new hotness.
React has been dominant for at least ten years and NextJS for a good fraction of that.
Thought experiment: assume the worst: next.js + eleventy is in decline; what does it change in the short-term? It is likely that people using those frameworks are getting things done in them. To me, the fact this whole discussion is happening illustrates how fickle devs are in this particular ecosystem. It's like nobody wants to be caught dead using something that might not be the new hotness.
React and NextJS are hardly "new hotness". React has been dominant for at least ten years and NextJS for a good fraction of that.
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…
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.
Earlier quoted context omitted.
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?
Earlier quoted context omitted.
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.