I'm totally not sold about this. Next.js routing was wrong from the start, and now it introduces a tons of new concepts that will inevitably require the rewrit

I'm totally not sold about this. Next.js routing was wrong from the start, and now it introduces a tons of new concepts that will inevitably require the rewriting of entire apps in a far future, since it will be "the new way to do routing in Next.js". What I really don't like is the coupling between the filesystem hierarchy and the actual routes, that is difficult to reason about when you have non english routes names with multiple route parameters. I mean, the routing problem for server side applications was solved a lot of time ago: a simple regex for the route definition, and the related handler that will responde to that route. I never understood why Next.js guys went with this inconvenient approach of the file system routing.