3 ms·
Useless anecdote: I don't have direct experience with Next.js[1] (but React, Angular, Vue, Solid), but I did help a co-worker out with something in their Next.j
by moogly 2y ago
Useless anecdote: I don't have direct experience with Next.js[1] (but React, Angular, Vue, Solid), but I did help a co-worker out with something in their Next.js app, and as soon as I saw the madness that was file-based routing I wrote off the whole thing.
[1]: mostly because I have never been interested in the modern form of SSR due to my controversial belief that that is a truly _insane_ solution to SEO, TTFB and page load performance. You don't really solve a problem by piling more problems on top, however many billion man-hours a whole industry spends on that endeavor.
- epolanski 2y agoI don't think file based routing is the evil, on Nuxt it works very well.
- wdb 2y agoFile-based routing is one of the best things to have up to particular size of an application. Makes navigating the code so much easier then routing spread throughout the code base
- bryanrasmussen 2y agoIf you have a single routes source that makes it just as easy, although that really depends on the people making sensible route handlers for the routes to point to, if people are not good at doing that obviously the implicit order of /pages is superior.
- bluefirebrand 2y agoYou shouldn't need to structure the codebase based on how the application is routed More importantly you shouldn't need to restructure the codebase if the application routing changes File based routing is a terrible idea
- moogly 2y agoMy exact visceral reaction.
- mmcnl 2y agoThe idea of hybrid web apps that combine SSR with CSR is actually very interesting. It allows for much richer experiences.