> Avoid self-hosting your compiler
Not sure this is so problematic anymore.
The Zig folks targeted WASM so that they can bootstrap without needing a second compiler implementation. Compilers don't need a lot of POSIX in order to be functional.
Not sure this is so problematic anymore.
The Zig folks targeted WASM so that they can bootstrap without needing a second compiler implementation. Compilers don't need a lot of POSIX in order to be functional.
The fact that Zig did a boatload of extra work due to path dependence is true.
However, this in no way contradicts that self-hosting via WASM/WASI is likely a far better idea than maintaining two complete compilers in different codebases and languages solely in order to bootstrap.
In fact, nowadays, someone building a new language and compiler is probably better off targeting WASM/WASI before any other architecture.
Welp, video: https://www.youtube.com/watch?v=MCfD7aIl-_E