Sure C is more convenient that C++ in a few domains, but I'd suspect that plenty of C fans that "hate C++" will find more to like in Zig. It's about the features it doesn't have.
I might personally describe that differently, as I felt like the GP was implying that C++ and Rust couldn't be used in the same space as C, which isn't quite true.
One challenge C++ has always had is that the language overhead, while easier in some contexts, didn't bring with it significant safety guarantees. As more people are introduced to safer, low overhead languages, I anticipate that to change.
Shout out for DABC, another really enjoyable-to-work-with system in that space!
Until then they are pretty much a competitor to what would be otherwise a userspace C application.
Assuming having a GC enabled language isn't an issue to meet application SLAs.
Naturally people port code from Python to Go.
It is what happens when one uses scripting languages for a full blown application and then discovers how slow it is.
Then Go gets choosen cause Google is cool and Oracle is bad.
Meanwhile corporations keep using Java, .NET, JavaScript and C++ as their main workhorses.
Go's selling points are Docker and Kubernetes, and not everyone is actually using them.
TCP/IP stack and file system utilities in Fucshia, Kubernetes, Android OpenGL/Vulkan debugger, UEFI replacement, DNS server
I think it is in the sense that you (usually) should never write network-facing C code.
Zig reads to me as something actually trying to displace C. Or C with no corner cases and some modern features.