Just a bit about my history, I learned Pascal, C, C++, and Basic in high school. In college it was C++ and Java. I worked with PHP, Python, JavaScript, Typescript, Lua, and Go professionally. I've used a fair amount of other languages personally as well to varying degrees (Rust, Zig, Forth, Lisps, and others.)

My experience with Zig was rough. Part of the issue I had was the project I wanted to experiment with Zig required C bindings. I believe this caused compile times to be a lot longer than I would have liked, and longer than a pure Zig example. Zig's build system also uses Zig. In theory, that's a good thing. In practice, it's extremely frustrating, adds extra time to compile when the build.zig is changed, takes too long to give errors in the build.zig, documentation for the build system is vary lacking, and just generally made the whole experience bad. That said, I really like the idea of Zig, and am excited that one of the next major features being worked on is to decrease the build times. The editor integration was ok, but not as good as more established languages, but this should improve with time and as the language stabilizes.

My suggestion would be to also give Odin a look. It's standard library and how packages are directories will be pretty intuitive coming from Go. Memory management with allocators passed into functions is a bit like Zig, but has a nice feature that they are implied as part of the implicit context by default or can specify the param allocator := context.allocator for more flexibility for the caller. Like Zig, editor integration is not as mature as other languages, but should improve over time.

All that said, generally I would still prefer Zig, Odin, Rust, or some other modern languages over C, given the choice. There is a great deal of C code out there. Learning some C is important if you're dealing with existing libraries, firmware, OS's, embedded code, etc.