1. 12
  1.  

  2. 2

    I just watched the talk the other day! You did a great job, but I was surprised there was no mention of WASI. Was there a reason you opted for making your own instead of implementing WASI? It seems to be feature complete enough to run programs using libc.

    1. 1

      Two main reasons:

      1. My work initially predates wasi.
      2. I don’t think wasi goes far enough in terms of presenting a next generation API. It has two different system calls for “write to file” and “write to socket” that’s bloat in my opinion. It should just be write.