Home | Notifications | New Note | Local | Federated | Search | Logout
Note Detail
Reply to @mcc@mastodon.social
mcc@mcc@mastodon.social (2025-06-04 13:02:38)
This post was supposed to have been inlined in this thread but I got distracted running to catch a bus and messed up. This isn't a bit I really am writing this thread at a series of bus stops today https://mastodon.social/@mcc/114622991386698840
(I want to emphasize this thread will make substantially less sense if you do not read at least the single post linked at this link)
---Reply---
mcc@mcc@mastodon.social (2025-07-14 12:50:54)
As a note, I have not so much as touched this stuff in the last five weeks. It might be the exceptionally bad quality of the documentation on WASM textual format has actually killed my 25 languages project. I've spent my junkfood-project time for the last month learning to make Game Boy games. Christine LM suggested I just ignore WAST and write my wasm stuff in Hoot (which is apparently her research group's LISP that compiles to Wasm) because that's intended for use by humans. Heck, maybe.
Reply
---Replies---
mcc@mcc@mastodon.social (2026-10-01 13:15:56)
OK. An update of how this attempt to write a small, simple program in textual WASM went.
I read the basics. It made sense. I attempted to write the simplest of code. I was immediately horrifically stymied by unreadable (apparently intended for implementors of validation tools, not coders) documentation, underdocumented and in other places literally unfinished tooling, the three (?) WASI standards, and different wasm targets (web, wasi) having entirely different ways of invoking "printf". (1/2)