firefly-boot VS Nim

Firefly, curly braces:

I'm still working on Firefly, a language with first class capabilities.

Since there's no other way for `deleteDirectory` to obtain capabilities than to recieve them as arguments, `deleteDirectory` only has access to the file system.

[1] https://github.com/Ahnfelt/firefly-boot/tree/master/compiler

> Do you have more to share, like resources about capability-safe languages, or your ongoing work?

I can share an example from the main function of the [self hosting Firefly compiler](https://github.com/Ahnfelt/firefly-boot/tree/master/compiler):

    main(system: System): Unit {

I'm working on Firefly, which will compile to JS once bootstrapping is complete (almost there).

Still working on typechecking Firefly with the help of a friend.

Working on the type inference for Firefly. I don't have a lot of free time at the moment, so it's coming along slowly.

Firefly uses object capabilities for enforcing purity:

In Firefly, this is done without macros:

Firefly - self hosting, working on the type inference.

22. Nim - $80,000

I think the right answer to your question would be NimLang[0]. In reality, if you're seeking to use this in any enterprise context, you'd most likely want to select the subset of C++ that makes sense for you or just use C#.

[0]https://nim-lang.org/

I don't think it's a rust-inspired language, but since it has strong typing and compiles to javascript, did you give a look at nim [0] ?

For what it takes, I find the language very expressive without the verbosity in rust that reminds me java. And it is also very flexible.

[0] : https://nim-lang.org/

I see a valid cert for https://nim-lang.org/

FYI, on the front page, https://nim-lang.org, in large type you have this:

> Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula.

You better off with using a compiled language.

If you interested in a language that's compiled, fast, but as easy and pleasant as Python - I'd recommend you take a look at [Nim](https://nim-lang.org).

And to prove what Nim's capable of - here's a cool repo with 100+ cli apps someone wrote in Nim: [c-blake/bu](https://github.com/c-blake/bu)

Chapel has at least several full-time developers at Cray/HPE and (I think) the US national labs, and has had some for almost two decades. That's much more than $100k.

Chapel is also just one of many other projects broadly interested in developing new programming languages for "high performance" programming. Out of that large field, Chapel is not especially related to the specific ideas or design goals of Mojo. Much more related are things like Codon (https://exaloop.io), and the metaprogramming models in Terra (https://terralang.org), Nim (https://nim-lang.org), and Zig (https://ziglang.org).

But Chapel is great! It has a lot of good ideas, especially for distributed-memory programming, which is its historical focus. It is more related to Legion (https://legion.stanford.edu, https://regent-lang.org), parallel & distributed Fortran, ZPL, etc.