Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://chaos.social/users/swetland/statuses/114623408015040642">Brian Swetland (swetland@chaos.social)'s status on Wednesday, 04-Jun-2025 14:20:46 JST</a><a href="https://chaos.social/@swetland" title="swetland@chaos.social"><img src="https://gnusocial.jp/avatar/110748-48-20230518202522.webp" width="48" height="48" alt="Brian Swetland" style="position: absolute; left: 0; top: 0;">Brian Swetland</a><div><a href="https://gnusocial.jp/notice/10095575" rel="in-reply-to">in reply to</a><ul><li><li><a href="https://gnusocial.jp/user/105710" title="whitequark@mastodon.social">✧✦Catherine✦✧</a></li></ul></div></section><article><p><a href="https://mastodon.social/@whitequark">@whitequark</a> <a href="https://mastodon.social/@mcc">@mcc</a> That definitely aligns with my experience trying to read it from a "how do I build a functional WASM runtime" and "how do I generate correct WASM binaries" standpoint.  </p><p>Some notes from my initial encounters with it illustrate specific grumbles with the presentation:<br><a href="https://chaos.social/@swetland/111271568378452789" rel="nofollow noreferrer">https://chaos.social/@swetland/111271568378452789</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/5146411#notice-10095602">In conversation</a><time datetime="2025-06-04T14:20:46+09:00" title="Wednesday, 04-Jun-2025 14:20:46 JST">about 16 days ago</time> <span>from <span><a href="https://chaos.social/@swetland/114623408015040642" rel="external" title="Sent from chaos.social via ActivityPub">chaos.social</a></span></span><a href="https://chaos.social/@swetland/114623408015040642">permalink</a><h4>Attachments</h4><ol><li><article><header><div>No result found on File_thumbnail lookup.</div><h5><a href="https://chaos.social/@swetland/111271568378452789">Brian Swetland (@swetland@chaos.social)</a></h5><div> from <span>Brian Swetland</span></div></header><div>Am I the only one who finds that the WASM spec takes a lot of effort to understand?I've been able to find answers to my questions, but it has taken a lot more time and effort than I'd expect for something that feels like a straightforward and sensible design. The presentation feels needlessly convoluted.I'd love a quick reference "green card" that lays out the bytecode and file format in the style of traditional CPU docs.#WebAssembly #Documentation</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Brian Swetland (swetland@chaos.social)'s status on Wednesday, 04-Jun-2025 14:20:46 JSTBrian Swetland
in reply to
- mcc
- ✧✦Catherine✦✧
@whitequark @mcc That definitely aligns with my experience trying to read it from a "how do I build a functional WASM runtime" and "how do I generate correct WASM binaries" standpoint.
Some notes from my initial encounters with it illustrate specific grumbles with the presentation:
https://chaos.social/@swetland/111271568378452789
In conversationabout 16 days ago from chaos.socialpermalink
Attachments
1. No result found on File_thumbnail lookup.
  Brian Swetland (@swetland@chaos.social)
  from Brian Swetland
  Am I the only one who finds that the WASM spec takes a lot of effort to understand? I've been able to find answers to my questions, but it has taken a lot more time and effort than I'd expect for something that feels like a straightforward and sensible design. The presentation feels needlessly convoluted. I'd love a quick reference "green card" that lays out the bytecode and file format in the style of traditional CPU docs. #WebAssembly #Documentation

Public

Embed Notice

HTML Code

Corresponding Notice