I much prefer the pattern I've noticed with the recent generation of Go projects. What I mean is that I find myself more and more often going to a project's repository to check for an issue or open a pull request, only to find that it is written in Go. After the initial hype cycle, Go silently started being the engine many useful tools were written in. While I understand that Zig needs to have some level of getting the word out early on, ultimately having great projects arrive that are written in Zig (that don't need a "written in Zig" tag line as a sort of marketing gimmick) would be the best statement. This pattern I've observed with Go holds true for projects written in TypeScript, Python, and even C as well but Go is the more recent entry.
Effectively, less focus on slogans and more on great projects that solve actual problems. Sometimes moving in silence can speak volumes. (In chess, there's a saying: "Move in silence. Only speak when it's time to say, 'Checkmate.'")
But your sentiment was great! :D
I rather love three specific projects that are rather vocal about Go actually.
TamaGo, TinyGo and the Go compiler toolchain itself.
As they are all good examples regarding Go's suitability for systems programming, regardless of the usual discussion of what is systems programming about.