... triggered when you click Copy under a message. Nothing exotic. I literally copied the cURL from the browser and pasted it into Rentgen. Then I let Rentgen do what it does best: mutate inputs. Result? Sending perfectly valid JSON strings just not valid UUIDs consistently triggered 500 errors. Cyrillic characters? 500. Accented letters? 500. Random symbols? 500. Even better: numbers and booleans returned 422, which means validation exists but only at type level. If it s a string

... tags. 100% free and open-source. Here's how it works: https://x.com/MaxPrilutskiy/stat... The core challenge we had was - how do you translate React components without touching the source code? Traditional i18n requires rewriting your entire codebase - extracting strings to JSON files, wrapping components in `<Translation />` tags, maintaining separate dictionaries. So, we asked ourselves: "What if that actually wasn't necessary?" AST So, we came up with this idea to processes React app's Abstract Syntax Tree ... ... need in building twice to see translations. Performance Large codebases, including ours, can't afford slow incremental builds, so performance was another beast entirely. We're talking about processing thousands of components, each potentially containing dozens of translatable strings

... Product Hunters, We launched our product yesterday and received many comments about machine translation vs. human translation: https://www.producthunt.com/post... It's a topic that fascinates me and I've been collecting fun machine translation failures for a long time, let me share with you some of my faves I speak some Mandarin Chinese and that's a great language for machine translation failures 1. There is this Chinese set phrase (= to be jealous; literally to eat vinegar ... ... hope you ll have a great ( beautiful ) future . 3. One of the key problems is that machine translation often doesn't get the context. It becomes especially serious if you translate standalone words (like UI or other short strings