As it compiles through C it can use many of the optimizations of the C compiler. The code it produces seems, in general, slightly slower than chicken, but with a more uneven profile.
On the other hand it seems like a nice environment! It uses cheney on the MTA, which mean free call/cc among some other things.
Other than that? It seems like package managers are finally coming to scheme. Good. Chicken has been the only one with a proper one for quite some time.
Roughly the same speed as chicken means fast enough for most tasks. Probably some orders of magnitude faster than python for things that are actually written in python and not just glue between C function calls.
..transpile to C for speed,
..have an interpreter (REPL) for convenience,
..use *Cheney on the MTA* to support:
....continuations
....1st generation of GC.
Making binaries for widespread OS is a good ability to have. That's one side of the whole thing: Where can I run it, when I am done or when I want to deploy?
It would be interesting to learn more about the available libraries and frameworks as well. Of course standard compliant Scheme code can probably be used. What else? Where can I get libraries from? To get to the need to run the software somewhere, one first needs to write it. Of course libraries can be of great help here. I would like to know, what the ecosystem looks like.
And the readme links to cyclone-winds package manager, which does have a few packages at https://github.com/cyclone-scheme/cyclone-winds/wiki. A little statement about being able or not able to use libraries from other Scheme's ecosystems might be good to add.
Does anyone know how this compares to Chicken scheme? It looks like they both are able to transpile to C and have good FFI support.