leucippe

6 ms·

1. 1.▲
   by leucippe 2y ago

   There's in-progress design work in SIG Embedded to eliminate unnecessary copies, because that will help using interfaces on embedded devices.
2. 2.▲
   by leucippe 2y ago

   For background, WASI 0.1 is one interface: a smaller POSIX. Translating POSIX's low-level ABI concepts into WASM is enough for this. WASI came out of WASM's goal of portability, and 0.1 makes WASM portable across POSIX systems. WA
3. 3.▲
   by leucippe 2y ago

   There's Dylibso's Extism, a WebAssembly plugin system. The company building it begins with D. https://www.dylibso.com/products/extism/
4. 4.▲
   by leucippe 2y ago

   Registers will keep growing. Rather than adding 512 bits to the spec, it's better to choose an abstraction that's portable across hardware, so that modules don't need to be recompiled every few years with the latest and great
5. 5.▲
   by leucippe 2y ago

   As much as binary size should be a problem for individual developers to deal with, I've seen how those individual developers treat Electron. There's no doubt in my mind that someone will ship 50 little JavaScript programs inside
6. 6.▲
   by leucippe 2y ago

   The plan is to support async without function colouring. I recommend this talk by Luke Wagner on async plans in WASI 0.3 ( https://youtu.be/y3x4-nQeXxc ) for background on how it will work. To summarise, from an API perspec