From: Greyson Jennings <tallesttower1@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] 9front WASM runtime
Date: Sun, 17 Sep 2023 02:59:13 -0700 [thread overview]
Message-ID: <CALimrBpg0+GYP8VydzvO04Sidg9T2f1FEPij0E_0=bTtwZefvA@mail.gmail.com> (raw)
In-Reply-To: <CA+ULb+vGg+1WaqcV92YRsOw0n0EMSwdvCRLVyFKNhk81nqWztQ@mail.gmail.com>
Ricket is now functional! It can also package wasm files to behave as
an executable. Thanks to Ori on the #cat-v channel for helping me make
this more p9-like.
https://github.com/SlashScreen/ricket
On Tue, Aug 8, 2023 at 3:59 AM Roman Shaposhnik <roman@shaposhnik.org> wrote:
>
> On Tue, Aug 8, 2023 at 4:09 AM Greyson Jennings <tallesttower1@gmail.com> wrote:
> >
> > I'd been tinkering around with WASM runtimes and I've managed to get a
> > functioning build for plan 9, called Ricket! It's basically a frontend for
> > wazero tailored to use in plan 9, and It's super in alpha, but it does run
> > basic command line applications. I thought you guys might find it
> > interesting, and if anyone finds it useful at all, I can continue tinkering
> > with it.
> >
> > I built it because while nearly every popular language can compile to WASM,
> > only Go, C, and sometimes Zig are the only languages I can think of that
> > have explicit Plan 9 support, and so I wanted to be able to have more
> > options for building CLI apps, and be able to easily port existing ones.
> >
> > Check it out on github here! The binary in the repository is compiled to p9
> > and it runs on my 9front install. Later, I'll set up github actions to
> > built it automatically, and I may mirror it on sourcehut or shithub too.
> > https://github.com/SlashScreen/ricket
>
> FWIW: I love it! Would like to play with it once it is a bit more developed.
>
> Thanks,
> Roman.
--
No newline at end of file.
prev parent reply other threads:[~2023-09-17 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 1:09 Greyson Jennings
2023-08-08 10:54 ` Roman Shaposhnik
2023-09-17 9:59 ` Greyson Jennings [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALimrBpg0+GYP8VydzvO04Sidg9T2f1FEPij0E_0=bTtwZefvA@mail.gmail.com' \
--to=tallesttower1@gmail.com \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).