maxpr

5 ms·

1.
Lingo.dev (YC F24) is hiring a senior content engineer (Remote, worldwide)(lingo.dev)
1 points by maxpr 1d ago
2.
Your Margin Is the AI Labs' Roadmap(maxprilutskiy.com)
3 points by maxpr 26d ago|0 comments
3.
Every RAG-based localization pipeline has the same blind spot(lingo.dev)
1 points by maxpr 4mo ago|0 comments
4.
by maxpr 1y ago
1. I do speak more than one language. I agree with your point that perfect localization requires seeing a element in the broader context of the parent component, parent page, the product, the industry, the audience and their expec
5.
by maxpr 1y ago
Historically, there are a couple of reasons why developers prefer to i18n their app instead of letting users do that. 1. PostHog has a great tool that lets developers "watch the video" of how users interact with their app's U
6.
by maxpr 1y ago
Thanks! =) > localization is far from just translating the text For sure, that's spot on. What I'm excited about the most is that linguistic/cultural aspects are close to being solved by LLMs, including Gemini 2.5 that&#x2
7.
by maxpr 1y ago
Good point. There are JavaScript tools that do that for js devs, but since oftentimes you end up having <a>links</a> and nested elements in the code, wrapping becomes problema
8.
by maxpr 1y ago
Yep, Cursor indeed helps! (Here's a battle tested prompt example we found working pretty nicely with claude o3 + claude 3.7: https://lingo.dev/cli/extract-keys ) > Then, you simply ask it to translate into other
9.
by maxpr 1y ago
I think modern Japanese is LTR, but besides that - I believe the project you worked in the past solves an important problem. Besides pluralization (and e.g. Arabic having 6 forms zero/one/two/few/many/other), turned
10.
by maxpr 1y ago
Perhaps I could've communicated this better, but we've built Lingo.dev Compiler for web apps and user interfaces, not for technical/professional content. And since we had to exclude certain terms like "Lingo.dev Compiler
11.
by maxpr 1y ago
we've added support for both these cases actually! :) 1. `data-lingo-skip` - excludes a jsx node from i18n 2. `data-lingo-override-<locale code>` - overrides version in <locale code> language with a custom value 3. also `da
12.
by maxpr 1y ago
Exactly, this is a great direction! We believe automatic discovery + i18n processing is the most natural next step for i18n on the web, since LLMs now exist. And we feel that not only will industry standard i18n libraries like i18next or re
13.
by maxpr 1y ago
I believe tRPC could be a great solution to separate logic, generally speaking. However it also depends on what type of logic - some logic, like state/behaviour of the sidebar/modals will always remain client side.
14.
by maxpr 1y ago
With the community support we hope to support more platforms soon vs now, but I can confidently say that adding support for techs stacks using one of the following: Vite Rollup webpack esbuild Rspack Rolldown Farm should be reasonably strai
15.
by maxpr 1y ago
Genuinely excited to read comments like yours. We started the project scratching our own itch, and are touched it resonated! It will remain 100% free and open-source. We're already dogfooding it on our website and app, so if you'd
16.
by maxpr 1y ago
Thanks for the perspective! We support larger org workflows with the Lingo.dev Engine product, but that's not the point: Lingo.dev Compiler is unrelated to that, 100% free and open source. We started with a thought - what if i18n is ac
17.
by maxpr 1y ago
woah, i like this domain name! I bet it cost you a fortune :)
18.
by maxpr 1y ago
Sure Jjani, perhaps our docs could be slightly better! :) Typically quality changes significantly with the right setup of translation fine-tuning settings, so send me a DM with your current setup and we'll help you out in a couple of m
19.
by maxpr 1y ago
Hey lukol, that's an exciting problem to solve. The best solution right now is prompt engineering: turns out, AI can be tuned to provide top quality results with the correct system prompt/few shot setup, and custom prompts can be
20.
by maxpr 1y ago
Interesting perspective. Unsure if I communicated it well, but unlike auto-translators such as Google Translate, this project leverages a context-aware LLM to recreate the meaning and intent of the original text in another language.
21.
by maxpr 1y ago
> half-assed translation that was obviously made by a machine That's exactly what we want to solve. Here's the thing: It turned out, AI translates better than humans when provided with enough correct context. Both macro context
22.
by maxpr 1y ago
Yep, localization is the best term here, but sometimes folks confuse it with other things, for example geo localization or localization of errors. So we usually try to use both terms at the same time, often interchangeably, though translati
23.
by maxpr 1y ago
Thanks! To make it work predictably, we actually tested quite a few different algorithms before landing on one that produces outputs LLMs can reliably understand. Conceptually, we're relying on common sense assumptions about how develo
24.
Show HN: Localize React apps without rewriting code(github.com)
89 points by maxpr 1y ago|72 comments
25.
HTML5 elements you didn't know you need(dev.to)
6 points by maxpr 1y ago|1 comments
26.
by maxpr 2y ago
Loving you guys have Typescript support from day one!
27.
by maxpr 2y ago
Looks very nice! Would be cool to see some wild animation styles, not designed for using in production at all, just some fun stuff. Emojis maybe or smth :)
28.
Supabase and Vercel Partnership(supabase.com)
21 points by maxpr 2y ago|0 comments
29.
by maxpr 2y ago
Disclaimer: I'm the tech co-founder at https://replexica.com . I like the idea. At Replexica we've basically built a better + much faster (+ sometimes cheaper) alternative to Lokalise, Phrase, and Crowdin (we help dev t