A C++-without-the-downsides language, an ungoogleable name, and 45k lines of proof

A one-person language that claims C++ power without the pain

The Ü programming language is a statically-typed compiled language built solo by a developer going by Panzerschrek since 2016. It reached the front page mostly on curiosity, and the thread spends its first half roasting the README before the author turns up to make the case the README couldn't.

RAII, LLVM, and a feature table that checks every box

The pitch: Ü is designed for programs that should be "both reliable and fast," leaning heavily on C++ and only lightly on Rust, with the explicit goal of being easier to use than Rust. Memory is managed via RAII — resource cleanup tied to object lifetime — with no garbage collector, and manual management allowed only inside unsafe blocks. The language claims to be memory-safe and race-condition-safe as long as unsafe code is avoided or written correctly, and ships templates, lambdas, coroutines, operator overloading, compile-time evaluation and inheritance-based polymorphism. It compiles via LLVM to x86, x86_64 and AArch64, with compilers written in both C++ and Ü itself.

The roast, the unanswered safety question, and the author's receipt

The README's tone drew immediate fire, especially one line promising the resemblance to other languages was "unintentional":

"Blessed are the humble, for they shall be humbled." — a commenter quoting the README's disclaimer

A more technical objection cut at the central safety claim, arguing RAII alone can't deliver it:

"with just RAII, you cannot even assign a class into a passed-in variable. The language designer must make more choices … maybe affine types, or linear types … How is this achieved?" — a commenter probing the memory-safety model

The reversal came when the creator stepped in — not with theory, but with a working codebase:

"The author here … Since November 2025 I develop a project written (almost) fully in Ü. It's a video game … I already have ~45000 lines of code … All this is manually-written (no LLMs involved) … No single time I needed finding/fixing memory-related issues … if something crashed, it was a safety check." — the language's author

The self-dunking continued in parallel — multiple commenters noted the name is literally ungoogleable, and one read the Fraktur-style umlaut logo as evoking imagery the author probably didn't intend.

Marketing lost the thread; the dogfooding won it

Ü is a near-perfect case of a project sabotaged by its own front page — an ungoogleable name, a salesy feature grid, and a logo that invites bad-faith reads. None of that touches the actual claim, which the author backed with the only evidence that counts in a one-person language: a real 45,000-line application, hand-written, that compiles and doesn't corrupt memory. Whether the safety model survives someone else's adversarial code is the open question the thread correctly raised and the README still doesn't answer.