[gosukiwi]

I'm writing a small side project app using Next.js. I found out the bad way that i18n support is quite bad. Sure, you get an i18n router, but you have to manage translations on your own. There are libraries to do it, which are fine, but translations only work in the front-end, there's no way to, for example, use translations inside an API call (!!).

Also, halfway through they decided to push a new Next.js version (still in beta) so you''ll need to move all your `/pages` to an `/app` folder, with a completely new structure.

I wanted to learn something new so that's fine, but something like Rails, Django or Laravel would have allowed me to develop way faster. I'm quite disappointed.

[samuelstros]

Can you elaborate on "manage translations on your own"?

I am working on dev-first localization infrastructure after being frustrated with i18n from a dev perspective myself. Your remarks seem like they fit into the infrastructure approach I am taking. See https://github.com/inlang/inlang

[gosukiwi]

Well what I meant there was just that the framework doesn't take care of that for you, you need a third-party library.