Zig does not have a good package manager, does it?
build.zig.zon discussion: https://zig.news/edyu/zig-package-manager-wtf-is-zon-2-0110-...
Example howto: https://ziggit.dev/t/how-to-package-a-zig-source-module-and-...
Actual docs: https://ziglang.org/download/0.11.0/release-notes.html#Packa...
This describes upcoming changes in zig 0.12 https://ziggit.dev/t/build-system-tricks/3531
It has the ability to pull in a package/module. However, I believe that having a "package manager" is explicitly an anti-goal.
I'm in agreement. It's become pretty clear that having any form of "package repository" without also allocating the necessary manpower to curate that repository causes disasters.
? it's literally one of the project's main milestones: https://github.com/ziglang/zig/projects?type=classic
Zig can manage packages. It can pull in a Zig package using a reference to a Git repository on GitHub, for example. It can pin that to a hash and cache it. It can specify dependencies. This is, strictly speaking, a "package manager" but is not what people normally think of when you mention that.
Zig does not have blessed mechanisms that pull from a central repository of packages. Having a central repository is normally what people think of when they talk about a "package manager" (node, cargo, deno, etc.). Yes, those managers could conceivably not use the central repository and specify everything explicitly, but nobody ever uses them like that.