> C is very close to the hardware, and it's pretty portable, too. Here you seem to be suggesting that portability is good, but then... > zig is supposed to b

> C is very close to the hardware, and it's pretty portable, too. Here you seem to be suggesting that portability is good, but then... > zig is supposed to be able to cross-compile really well, so maybe you can skip that ... you seem to be suggesting that this project should give up its (already existing!) portability. Without saying why. In 2016, it's not clear at all why having having a compiled language be self-hosting should be considered a worthy goal. It's just a lot of busywork instead of simply using an existing toolchain. Certainly not the right thing to do from a software engineering point of view. Certainly not the right thing to do if you want portability. Certainly not the right thing to do if you want interoperability with existing sanitizers. Certainly not the right thing to do if you want powerful optimizations. I'd agree that the frontend should probably be bootstrapped, at some point. But the whole toolchain? Just to avoid random HN commenters throwing "every self-respecting programming language is bootstrapped" at you? Nah.