> String methods cover case conversion, trimming, searching, splitting, replacing, padding, classification, and parsing. .len() counts Unicode codepoints, not bytes; use .bytes().len() for raw byte length. Indexing with s[i] works in bytes; negative indices count from the end and out-of-bounds returns null. Several methods have aliases: .find() / .index_of(), .ltrim() / .trim_start(), etc.
Indexing uses bytes and len uses codepoints? Are you mad?
weirdUnicode[weirdUnicode.len()-1] returns random char?
And a = "a"; a[1] is null??
xslang.org also looks great and I found the text in the guide + docs to be easy to read. I usually have to read C#/TS docs, so it was refreshingly terse.
What does it do differently? What problem it solves that other languages don't?
Also, performance numbers. This looks highly complex and I worry that your C backend would underperform similar code in other languages. So let's us know.
1: http://atari-xt.com/ (I really ought to get on that SSL cert, I guess)
Like the built in decorators. I think language design based on what people want to achieve rather than creating the most generic zoo of primitives is underexplored. So this is good.
It works pretty well!
Then... what people want to achieve changes, maybe they want to write a web app instead of desktop, and then you're screwed. Perl was excellent when everything was text... but when things started being XML or JSON or whatever, less so.
It's a fair point though, languages built around practicality have their place.
- JS
- Go
- Java
- Python
I think adding a page about that in the docs could help evaluate the language.
You can improve it by giving a reason for people to want to adopt it. That is bring novel ideas and push the envelope.
As is, it's a very impressive homework.
How's FFI with it? Can we just link any C lib?
How does it compare to others?
Is it C with bells and whistles?
Is it C++ with blubber removed?
How is it different from D?
From Go?
...
Trying to fish out from a multi-page reference what makes your language unique and what gripes with other languages it solves is tedious, very few people would do it. It's on you to explain it.
Afaic this is DOA, there is no excuse in implementing the core toolchain of a new language in a memory-unsafe manner in 2026.