3 ms·
I currently use NextJS at work and really don't recommend it for new projects. It's popularity is manufactured, not based on an organic desire by developers to
by syndicatedjelly 2y ago
I currently use NextJS at work and really don't recommend it for new projects. It's popularity is manufactured, not based on an organic desire by developers to use NextJS. Server actions are a poor/leaky abstraction unless you "ride the rails" of their use cases. The documentation is rather poor once the application's use cases become even moderately complex.
- verdverm 2y agoI chose NextJS because it's better than the alternatives, having tried them. I would disagree that it's manufactured popularity It's a layer on React and you can keep things simple from the server actions point of view (they are still pretty new in React proper too) Docs... It's react, they don't need to write that documentation, just the nextjs parts. I have had no major issues with their docs, not sure what you mean by moderately complex thing
- langcss 2y agoDocs are good but the app router complicated things and had a knock on effect on other docs like auth. Every example was app or pages now so you had lots of examples out there that could no longer work for you. That choice made the documentation a lot harder to use.
- solardev 2y agoI don't think next is necessary (or even right) for every project, but what do you mean its popularity was manufactured? It wasn't even around until a few years ago and it quickly displaced other frameworks.
- langcss 2y agoNextJS can be used in different ways, but it is solid as a front-end only set up for building React apps. Create-react-app is deprecated so the choices are fewer. Vite is another choice. Another is esbuild and a bit more set-up work.