firefly-boot VS starlight

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.

I have great news

Hello to all! This crate implements Shadow Stack algorithm which allows to track GC objects on stack with almost zero overhead! This algorithm is used inside Restricted Python and seems to work very well. This crate soon will replace DIY shadow stack implementation in starlight(JS engine in Rust) too.

Working on startup snapshots in starlight. I already have very basic implementation which allows to initialize runtime in just 17 microseconds from snapshot vs 23 microseconds without snapshot when every builtin is created from scratch. Future work is aimed mostly on making deserialization faster

Hi to all! I'm working on starlight (JS engine in Rust) and I can't choose memory management technique: Right now I have conservative on stack precise on heap GC which somehow manages to work but still has segfaults and I'm also working on rcgc feature which will use RC as GC algorithm but my main question: is it worth using RC over tracing cycle and how hard it will be to implement JIT when RC is used? I've never seen any runtimes that use RC and implement JIT.

There's test262_passed file in repo, you can take a look at what tests pass :)