Wasm is such a cool technology. The spec though for me leaves a lot to be desired. Oh, the first few chapters are fine, but when you get to the binary and text formats that's when it all breaks down for me. For whatever reason, Wasm loves OCaml. This wouldn't really be a bad thing if they didn't come up with their own custom language to denote syntactic elements of both formats instead of using EBNF or similar. I dis…
Despite not being an ML programmer, I found the spec pretty easy to read for the most part. One of the least intimidating specifications I have ever read, surprisingly.
WebAssembly from the Ground Up
51–60 of 61 posts
Re: WebAssembly from the Ground Up
#52Oddly enough, Zig is the nicest C to WebAssembly compiler I've used so far.
Re: WebAssembly from the Ground Up
#53Re: WebAssembly from the Ground Up
#54Re: WebAssembly from the Ground Up
#55Wasm is such a cool technology. The spec though for me leaves a lot to be desired. Oh, the first few chapters are fine, but when you get to the binary and text formats that's when it all breaks down for me. For whatever reason, Wasm loves OCaml. This wouldn't really be a bad thing if they didn't come up with their own custom language to denote syntactic elements of both formats instead of using EBNF or similar. I dis…
Their SpecTec system is fancy and neat but I don't think that auto-generated specifications produce something worth reading. Perhaps in the future when there's less churn, there might be a hand-written specification? In the mean time I've needed to jump into their Discord to ask clarification questions about the high-level stuff. Once understanding that and the grammar conventions and the like, the specification becomes much more readable, though still not great.
Certainly nothing like an RFC. But maybe I have too high standards...
Re: WebAssembly from the Ground Up
#56Wasm is such a cool technology. The spec though for me leaves a lot to be desired. Oh, the first few chapters are fine, but when you get to the binary and text formats that's when it all breaks down for me. For whatever reason, Wasm loves OCaml. This wouldn't really be a bad thing if they didn't come up with their own custom language to denote syntactic elements of both formats instead of using EBNF or similar. I dis…
Yes, I have had the same experience with the specification. It really is quite difficult to follow :c Their SpecTec system is fancy and neat but I don't think that auto-generated specifications produce something worth reading. Perhaps in the future when there's less churn, there might be a hand-written specification? In the mean time I've needed to jump into their Discord to ask clarification questions about the high…
Re: WebAssembly from the Ground Up
#57Is it possible yet to write a high performance concurrent garbage collector in WebAssembly?
Unless by high performance you mean something more specific.
With wasm-gc you get the GC "for free" (from the host), you can still write your own if you want but you loose the interoperability that wasm-gc solves.
Re: WebAssembly from the Ground Up
#58WebAssembly seems like a big workaround for JavaScript only supporting doubles, strings, and objects/arrays. Its big features are to allow using a byte array as stack/heap storage memory, and having actual integer types, along with allowing C code to be compiled to WebAssembly. Oddly enough, Zig is the nicest C to WebAssembly compiler I've used so far.
Re: WebAssembly from the Ground Up
#59What's the state of wasm for porting multi-process code? I want to run something that execs a command line tool, both in the browser. Doable yet?
most of that is happening above the WebAssembly spec: https://wasi.dev/ More specifically for command line tools: - https://wasi.dev/interfaces#presentation - https://github.com/WebAssembly/wasi-cli
Re: WebAssembly from the Ground Up
#60Just went and bought it! I'm in a process where application-level programming isn't cutting it anymore (I still have a lot to learn, but it's in the diminishing returns). I've been looking to understand the entire stack at a deeper level (from how requests are made to how they're parsed), and this seems like the next natural step! Thanks a bunch!