I can't answer as to why the current version is R4RS specifically. The original version Marc and I wrote was running a subset of R4RS. We tried to minimize the code as much as possible (hitting the 4K mark), so it's very possible we just wanted to get everything out of the way (it has been a while)
One of our goals was to reduce as much as possible a R4RS compliant REPL, because it is quite reasonably sized and doesn't support macros (we managed to fit it in 6.5KB!). We considered R7RS, but it was a bit too ambitious for a first goal. We plan on supporting R7RS eventually !
If you want to read more, section 4 of "A R4RS Compliant REPL in 7 KB" explains our rationale behind the choice of R4RS :
Good to see it has moved so much from just JavaScript being the main target. I like the small scheme portable idea a lot. For those requiring just a minimal scheme this works.
IIRC (might be wrong here) we had full support for JS, C, Python and Scheme from the start. As it evolved I'm unsure how support was kept throughout the versions but I know a much larger set of languages now support the runtime, at least for a subset of the features.
IIRC (might be wrong here) we had full support for JS, C, Python and Scheme from the start
I'm pretty sure we had support for JS, C, Python from the beginning as well. Then Scheme, posix shell, assembly came along for the ride.
I'm unsure how support was kept throughout the versions but I know a much larger set of languages now support the runtime, at least for a subset of the features
I'm really happy to see that the project is getting some attention! We made a lot of progress since the last post on HN (https://news.ycombinator.com/item?id=31096771). We are now fully R4RS compliant, support 16 different target languages with a sort of FFI with all of them.
We are currently working on flonum/bignum support and a guide for adding your own RVM (new host) so that you can run scheme in your favourite language. It should be coming soon!
I'll stay up to answer any questions about Ribbit!
Could Scheme ever run on a GPU? I've seen a GPU REPL made with APL. I'm not sure what graphics primitive could map to linked lists but it would mean John McCarthy's AI on modern AI hardware.
Implementing an RVM running on a GPU is definitely feasible, however, I'm not sure if it would be fast or efficient. For the case of Ribbit, you only need to write an RVM in a language that can compile to a GPU. An RVM is mostly a interpreter loop with some primitives. Maybe exposing the GPU primitives could enable heavily parallelizable scheme code ? It could be a fun experiment
Hi!
One of the original author of Ribbit here, glad to see it is still getting attention. Léonard and Marc took the project much further than I imagined.
As a fun fact, the project started as a riff of Justine Tunney's famous https://justine.lol/sectorlisp/.
For the interested, my new favorite project from Marc's team is https://github.com/udem-dlteam/pnut
Why R4RS? Was that just the standard at the time? I know R6RS is kind of huge and difficult, but R7RS seems pretty reasonably sized.
I can't answer as to why the current version is R4RS specifically. The original version Marc and I wrote was running a subset of R4RS. We tried to minimize the code as much as possible (hitting the 4K mark), so it's very possible we just wanted to get everything out of the way (it has been a while)
Hi! One of the authors of Ribbit here (@leo-ard).
One of our goals was to reduce as much as possible a R4RS compliant REPL, because it is quite reasonably sized and doesn't support macros (we managed to fit it in 6.5KB!). We considered R7RS, but it was a bit too ambitious for a first goal. We plan on supporting R7RS eventually !
If you want to read more, section 4 of "A R4RS Compliant REPL in 7 KB" explains our rationale behind the choice of R4RS :
https://arxiv.org/pdf/2310.13589
6.5K ! you could fit that on some microcontrollers
Good to see it has moved so much from just JavaScript being the main target. I like the small scheme portable idea a lot. For those requiring just a minimal scheme this works.
IIRC (might be wrong here) we had full support for JS, C, Python and Scheme from the start. As it evolved I'm unsure how support was kept throughout the versions but I know a much larger set of languages now support the runtime, at least for a subset of the features.
I'm pretty sure we had support for JS, C, Python from the beginning as well. Then Scheme, posix shell, assembly came along for the ride.
One thing that really helped is CI testing! All the RVMs (the 16 targets) are now fully tested at each PR (https://github.com/udem-dlteam/ribbit/actions)
Hey ! One of the authors of Ribbit (https://github.com/leo-ard).
I'm really happy to see that the project is getting some attention! We made a lot of progress since the last post on HN (https://news.ycombinator.com/item?id=31096771). We are now fully R4RS compliant, support 16 different target languages with a sort of FFI with all of them.
We are currently working on flonum/bignum support and a guide for adding your own RVM (new host) so that you can run scheme in your favourite language. It should be coming soon!
I'll stay up to answer any questions about Ribbit!
Could Scheme ever run on a GPU? I've seen a GPU REPL made with APL. I'm not sure what graphics primitive could map to linked lists but it would mean John McCarthy's AI on modern AI hardware.
Implementing an RVM running on a GPU is definitely feasible, however, I'm not sure if it would be fast or efficient. For the case of Ribbit, you only need to write an RVM in a language that can compile to a GPU. An RVM is mostly a interpreter loop with some primitives. Maybe exposing the GPU primitives could enable heavily parallelizable scheme code ? It could be a fun experiment