firefly-boot VS pen

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.

The Pen programming language is a new parallel, concurrent, statically typed, functional programming language. I'm excited to announce its v0.4 release here!

In this post, I describe my experience and some caveats about implementing and gaining benefits from the Perceus RC. I've been developing a programming language called Pen and implemented a large part of the Perceus RC there. I hope this post helps someone who is implementing the algorithm or even deciding if it's worth implementing it in their own languages.

I'm a developer of the Pen programming language. Since the last v0.3 release, many features have been implemented including async/await and concurrent runtime.