2 ms·
I have to agree that with the introduction of React 18, and the new versions of Next and SSR everything has taken a turn for the worse. I’m sure it’s all very f
by Aeolun 3y ago
I have to agree that with the introduction of React 18, and the new versions of Next and SSR everything has taken a turn for the worse. I’m sure it’s all very fancy and advanced, but it’s become completely impossible to reason about.
- teaearlgraycold 3y agoThe new Next has jumped the shark. I wish there was a good alternative right now. I feel like they’re building for FE devs who are scared to learn BE dev.
- 0xblinq 3y agoSo far I’ve found some shelter in Remix. But I’m skeptical they won’t fuck up as well. They have a reputation of breaking everything with react router.
- maronato 3y agoI feel the same. After a year of not touching Next, I came back last week to find it’s unrecognizable. It feels like there are 10 ways of accomplishing the same things now, and Next tries very hard to make none of them feel like the right way. Want to structure your code? There are 4 ways to do it. Want to fetch data? You can use route handlers, server components, or server actions. Don’t forget to choose one of the 5 ways to cache and revalidate data! Want to show a loading indicator while the data loads? There are a few ways to do it, but be careful because some ways depend of parent components being server or client side! Not to mention all of the “unstable” apis. I appreciate that they want to make it easier to build incredibly efficient applications, but now there are so many options and so many ways to shoot yourself in the foot that I’m stuck with choice paralysis. IMO a good framework should have one and only one obvious way to accomplish something. More advanced use cases should be hidden away in the reference documentation or left as an exercise. That’s why frameworks like Django and Rails were so successful.