I might buy your argument except that without corporate sponsorship for zig several projects using a very young and unfinished zig exhibit world class performance and utility, apparently without herculean effort.
Unfortunately it makes the libraries difficult (or at least very tedious) to read. I find zig's standard library a very good reference for figuring out to do things in application space, from what I've seen it's been very clear and useful.
I don't think manual memory management is c's problem. a very large number of errors i see in 'c' programs comes from the null terminated string paradigm and also mistakes from raw pointer manipulation (slices/fat pointers help a lot here).
I don't think D brought enough new to the table. I had already been coding in c++ for a while and was getting tired of all the little things wrong with c++. While D cleaned up a few things it was already too complex for my taste. And the whole GC thing followed by the D2 fiasco and I lost interest. When dipping my toes into Rust I also got the same vibe from it that I had from D. Too much complexity built in. I guess that made me a sucker for Zig because it is able to combine simplicity, cleverness, clarity and high performance.
I don't think zig is that much more complex than golang, with a (currently) crappier standard library. The bonus being you leave no performance on the table. I wonder if it would work with devops, where both c++ and rust fails.
Zig is simple, clever and clean. certainly not perfect but it addresses much of what I disliked about c++. I wanted to like D and rust but they seem just as complex as c++. Yes, better in some ways but still full of complexity.
Custom allocators in c++ was never enjoyable nor easy. It introduces more template slop everywhere. That's one thing I really liked about eastl, it did allocators much better. But it wasn't maintained.
Both go and rust had substantial dedicated corp support and dollars behind them. Zig not so much. With that in view its advancement is pretty remarkable.
Go doesn't belong in this discussion.its a better java, c#, python and not much more. It doesn't work for 24/7 or for performance sensitive applications.
People seem to underestimate this. One of the first reasons I noticed about c++ was trying to figure out what functions were being called in an overly complex inheritance hierarchy. The next was from hidden behavior from seemingly benign looking sequence of statements. Both of these are a barrier of entry for bringing in new coders to a complex code base.
The anti rust sentiment in large part is dissatisfaction with rust itself. Ziglang.org lists 3 principles of zig: no hidden control flow, no hidden memory allocations, no macros. This is not anti rust for the sake of being anti rust, this is anti lots of popular languages, and I personally like it.
The answer there was to always write small standalone executable unit test sets and simulation for day to day coding. Avoiding template heavy pigs like QT or boost helps too.
Compilation speed makes go nice. Zig should end up being king here depending on comptime use (ie: lack of operators can be overcome by using comptime to parse formulae strings for things like geometric algebra).
We can always dream about the unicorn language. In my opinion zig is the closest I've seen. Simple and orthogonal yet brilliantly extensible with its comptime. But it's not without its warts. And it doesn't annoy me like Rust seems to. (long time c++ programmer here who is weary of the ever growing complexities).
I had a 3060 12g in my daughters computer. It would freeze every couple of weeks for who knows what reason. Swapped out her mobo/CPU/ram with mine and it still froze. Put in an rx5709xt and it's all good now. The 3060 is now in a server. I would have gotten the card if someone at work hasn't sold it to me for 100$. What originally made me leave Nvidia was because of how quickly Nvidia dropped driver support for not very old cards but I can't remember what card I had at the time.
My experience is the opposite. Epgot a hold of a bunch of floppies in 1991. Dual booted so I could play Diablo. Some time around '98/99 got tired of dual booting.
Steam getting proton was a godsend, all those years of games became playable so now I have a huge back catalog.
Having coffee almost 30 years in c++ I really good tired of the complexity of it. Some of the newer complexity being workarounds for (in retrospect) poor decisions made decades ago. Build system situation never helped, and I still despise cmake. When D came out I was interested but garbage collection immediately turned me off, in my opinion the boost shared pointers (later adopted into the standard) solved and shut the door on memory leaks as a serious issue.
And then the d2 fiasco sort of blew it all up. Doesn't help that the language always felt very heavy to me. Likewise Rust feels heavy and cumbersome itself.
So it ends up that I'm another one of those who feels the itch getting scratched by zig.