perpetual-fallback-licenses VS simplelocalize-cli

> I don't see how these are user hostile.

They lock you in to continuing to pay even when you no longer derive value.

Say you stopped using Photoshop years ago, but suddenly need to export one of your old documents. You’re now forced to pay rent to Adobe for at least one month to access one of your own files. And Adobe won’t make it easy to unsubscribe again, which adds to the hassle.

> The pay per update model forces the creator to release big feature updates, even if the features are just bloat, as bug fix releases and stability work will usually sell much worse. That's mostly fixed by the subscription model.

Perpetual fallback licenses[1] solve that issue without forcing users to keep paying rent.

[1]: https://github.com/vitorgalvao/perpetual-fallback-licenses

shamless plug You can use my app for that, it doesn’t require monthly subscription. 😉

In favor of typesafe-i18n: - Offers an option for asynchronous loading of locales. It's in the roadmap for i18nifty but as of today it doesn't features it. - It's lighter 1.3Kb vs 22Kb for i18nifty (I could work on reducing the size but it isn't high in my priorities). - Support third party localisation services such as https://locize.com/ https://lokalise.com/ or https://simplelocalize.io/.

NextJS, a well-known framework among React developers, provides multiple libraries that create a very developer-friendly environment. The most popular ones are i18Next, next-translate and, our main focus in this blog post, next-18next, a translation library that does a fantastic job helping in translation management. The following blog post will show you how to set up next-i18n in your NextJS app and manage translations with SimpleLocalize. Take a look at our demo app for the reference.

own SaaS my salary is now higher than before 😌

I know the advantage of this approach is that you can do it for free, but in general you could also use something like SimpleLocalize (I’m the author, backend uses Spring and Java 18😎) You can keep translations there, auto-translate and host them on CDN. In my approach, the cool thing is that you can fix the incorrect auto-translated texts in the editor. It supports DeepL and Google Translate, there is a free forever plan and free 14-day trial.

Wow, that’s great! I was thinking that you used some kind of software like SimpleLocalize to use auto-translation. :)

Don’t implement it on your own. Use something like SimpleLocalize and use their REST API and CDN. Client will have a nice panel to edit/change translations and you will get a nice API to fetch translated content.