Blessed are the humble, for they shall be humbled.

As someone building a language myself, I'm interested in the other languages actively in development...

But you start with an info dump, no examples, and then a table of features - where the first feature is not something anyone would pick a language for.

You claim to be a memory safe language... And those are buried in the middle of the list. You want to highlight that, and say how you accomplish it. You say you have no GC, but no mention of Affine Ownership or Ref Counting. You talk about thread safety, but no mention of how.

You need to show WHY anyone should care about your language, what problem it's solving, and what that looks like as fast as possible.

In your comparison table, you leave out Go and include Odin - that seems like a mistake. Go punches FAR above its weight class. Dismissing it because it "comes with a heavy runtime" is likely to get your project dismissed, no offense. Odin is - essentially - experimental.

People's attention is fleeting.

Everyone and their mother is building a language or two...

Some things I want to know right away:

1) what stage are you at (honestly, not wishfully)?

2) what problems have you ACTUALLY solved instead of INTEND to solve at some point in the future?

3) how thorough is your testing, what do you have, how much, what's the coverage by category?

4) this seems like a performance language - I want benchmarks. If you don't have a good concurrency story, you better have something, and you better have convincing benchmarks that it actually works, otherwise - why is anyone from Go or Rust or Zig or Nim or Crystal or Swift or even Java/Kotlin/Scala or C# going to think about switching?

Saying "using RAII for memory management" is insufficient - with just RAII, you cannot even assign a class into a passed-in variable. The language designer _must_ make make more choices to get a useful language - maybe affine types, or linear types, or prohibit many C++-like idioms, or maybe just good-old refcounted shared pointers (but I'd argue this is a form of GC...)

> Ü is memory-safe and race-condition-safe, as long as no unsafe code is involved at all or as long as unsafe code is correctly written.

How is this achieved? The docs mention in passing that there is some sort of thread-safe immutable structs, but it is not really clear what's the overall picture and how they interact with non-trivial code. And the examples have nothing on thread.

Edit: also the name is ungoogleable.