It’s written in C, so you could compile that to wasm and then compile & run all inside the browser (I guess, assuming wasm is cool with that sort of thing, not a wasm guy here).

On the other hand, Hoot supports WASM-GC on release [0], and has had wasm support for a few years now. (Though Safari support has been a pain point - they've found a few bugs in WebKit's wasm support.)

[0] https://spritely.institute/news/hoot-0-6-1-released.html

Hoot (uses Guile Scheme), mentioned above, has a working interpreter, to quote...

   "The toolchain is self-contained and even features a Wasm interpreter for testing Hoot binaries without leaving the Guile REPL."

Hoot looks fantastic. There's a side project, Goblins https://spritely.institute/goblins/ that does distributed development too.

Great to see that people are still supporting Scheme tools. There's a lot of utility here, even if people (and job adds) go for the "latest" tools.

What does this mean?

There are plenty of problems with it:

https://okmij.org/ftp/continuations/against-callcc.html

People do not generally want to capture the entire continuation, they want delimiters. Delimited continuations are a superset of call/cc and vastly more useful, more performant and easier to understand.

The call/cc interface is completely backwards as well. It's like throw/catch but the exception handler is specified by throw instead of catch. Totally mind bending and unintuitive.

This continuation business is just resumable exceptions. Would have been a lot easier for people to understand and use had they just called it that.

  try:
    print(10 + throw("error"))
  catch error, continuation:
    continuation(10) # Makes throw return 10, prints 20