MarineCG40

4 ms·

1. 1.▲
   by MarineCG40 11mo ago

   I recently found a really practical way to detect and fill missing translations when working with i18next and honestly, it saves a ton of time when you have dozens of JSON files to maintain. Step 1 — Test for missing translations You can no
2. 2.▲
   Next-internationalizationext vs. next-intl vs. intlayer(intlayer.org)

   2 points by MarineCG40 1y ago|1 comments
3. 3.▲
   by MarineCG40 1y ago

   If you’ve tried adding multiple languages to a Next.js app, you know it can be a pain: * Big JSON files full of keys * Forgetting to add a translation * Config that makes no sense Here are the 3 main options people use: next-intl – super s
4. 4.▲
   Stop fine-tuning LLMs for docs, use RAG(intlayer.org)

   2 points by MarineCG40 1y ago|1 comments
5. 5.▲
   by MarineCG40 1y ago

   I keep seeing people fine-tune LLMs for use cases where they probably don’t need to. In most doc/product scenarios, you don’t need another fine-tuned model—you just need retrieval-augmented generation (RAG). Why I think RAG wins in mos
6. 6.▲
   by MarineCG40 1y ago

   Reach me out if you implement it
7. 7.▲
   by MarineCG40 1y ago

   Tell me more when you try it !
8. 8.▲
   Show HN: A simpler way to manage internationalization in component-based apps(github.com)

   6 points by MarineCG40 1y ago|6 comments
9. 9.▲
   Show HN: A component-first approach to internationalization(github.com)

   5 points by MarineCG40 1y ago|0 comments