What does HackerNews think of jakt?

Jakt [1] shares your design philosophy, and has implemented syntax like this: [2]

    guard foo is Bar(x) else {
        println("not matched")
        return -1 as! c_int
    }
    println("hello there: {}", x)

[1]: https://github.com/SerenityOS/jakt

[2]: https://github.com/SerenityOS/jakt/blob/main/samples/guard/i...

SerenityOS is doing exactly that:

https://github.com/SerenityOS/serenity/tree/master/Ladybird

I also like their Jakt programming language:

https://github.com/SerenityOS/jakt

Though I'm more enthusiastic about Redox (doing it in Rust):

https://gitlab.redox-os.org/redox-os/redox/

I can't find the direct link either, but the blog post is quoted as the reason for leaving the Rust project.

Neither happens in a vacuum. There was likely a lot of internet and real-life drama between people. The basis for the blog post already shows some sign of preexisting drama.

I don't know the context so I can only theorize why they quit.

Perhaps they noticed the drama beforehand and this was the final straw. Perhaps they felt called out by the blog post. Perhaps they saw more internet drama coming and decided they've had enough.

Maybe of note: JT has been very influential in a new language originating from the SerenityOS project, Jakt [1], though his contributions died off over time. Perhaps they're searching for a new challenge and saw this as a good moment to get out?

[1]: https://github.com/SerenityOS/jakt

It's very opinionated and SerenityOS-focused, but the language Jakt ( https://github.com/SerenityOS/jakt ) transpiles to C++, has memory safety and some very neat ideas for readability.

I love Rust, but its model and specifics would make it difficult to learn how to write code in other languages.

For low-level code, I think Carbon may fill that niche in the future. If it doesn't, C++ may be a good candidate once up-to-date books have been written and compilers actually support the modern spec. Classrooms/guides would need to move away from the still-lingering "C++ is C with classes" approach and use the standard library before that can be a reality, but this book[0] by Bjarne Stroustrup himself demonstrates the future C++ _could_ have if all the modern language features become usable.

In business, C++ will still be the domain of ancient clusterfucks compiled by MSVC++ 6 in many areas, similar to how most Java code is still built around Java 8 because that was the most recent stable version for many projects' lifecycle (and Oracle's decision to only ship JRE 8 to consumers doesn't help) and how .NET 4 is still taught in schools because the new and scary dotnet tool doesn't map 1-to-1 with the old way of working. I can't imagine microcontroller toolkits supporting a modern version of _any_ language in the first place.

However, if more people would learn modern C++ (or a replacement, like Carbon), I think this class of programming languages can have the same growth and hype Rust has enjoyed for the past years.

I'm keeping my eye on Carbon and Zig. Google's influence has managed to push Go to the forefront despite its many quirks, and Zig seems to be focused on doing "C, but right" rather than "C++, but right" which so far is looking pretty promising.

It's also fun to see Jakt[1] being developed in real time; I don't think it's a language that will be useful for production software any time soon, but on the other hand it's a language that actually produces binaries reliably (unlike pre-alpha Carbon or pre-release Zig, the latter exposing many problems after switching to a self-hosted compiler).

[0]: https://www.stroustrup.com/tour3.html

[1]: https://github.com/SerenityOS/jakt

I really like Jakt:

https://github.com/SerenityOS/jakt

> It would have been much more interesting to have ladybird written in plain and simple C (with the right compile-time and runtime function tables and NOT compiling with only gcc or clang). Maybe it is not too late to fix that.

Quite the opposite. The serenityOS people are implementing their own programming language, [jakt](https://github.com/SerenityOS/jakt), which currently compiles to C++, and they'll move the codebase progressively to it as they go. I personally doubt that the project could have moved so fast in just a few years if it had been using C instead of C++.

Shave a few Yaks :)

No, kidding... But their Jakt[1] language will make it much easier to contribute than in arcane reality of C++.

[1]: https://github.com/SerenityOS/jakt