The magical thing here are C header files. While it is certainly possible to crosscompile using traditional tooling, what zig does here is an all-in-one package that lets you cross-compile not only to a different architecture, but a different libc or operating system. Most impressive is it’s support for selecting target glibc version.

Actually there was some effort (I think currently on halt) to make those headers usable outside of zig. So yeah, it’s not a thing that is (or rather must be) zig specific, but right now zig is the only language that does that AFAIK

I read that as well and Andrew explained that although he wants to do that, it won’t happen immediately. There are large projects that rely on this feature and he asked for their input on this topic.

Another thing is that proposed change is to remove clang from the zig distribution. It would still be possible to depend on a zig package that provides an interface to seamlessly compile with system clang.