Zig: All Package Management Functionality Moved from Compiler to Build System

nesarkvechnep

Development of Zig feels so wholesome.

vitaminCPP

I've read somewhere that the longer-term goal is to move the build system into a WebAssembly VM. If so, this is incredible.

malkia

Everytime I see a language creating their own package system, all I can think of it how much we've missed here. The only exception is C/C++, where there is none established that well, for good or bad. These choices may create later super-convoluted processes when you have to mix more than one language together. Packaging systems makes thing easy, but complicate further the line if another language needs to be used.

arikrahman

A very well-reasoned separation of concerns.

hoppp

Good for zig. I am very tempted to switch from go to zig but also enjoying things from the sidelines.

chabska

Zig, Go, and Python developers do this thing, where they announce that "We have removed the radiator fluid from the fuel tank", and all their supporters cheer about how this is good for the language, how performance will surely improve significantly, and I'm over here wondering why did they put the radiator fluid in the fuel tank in the first place.

goranmoomin

So this is the change that forced Zig to remove @cImport (and into the build system), right? I know that it’s purely a UX concern, and that the changes (to decouple the build system and the compiler) are pretty critical for the maintainers, but it’s still a bit sad that development sanity comes first than the UX. (It’s the right call, just that it’s sad.) @cImport was a big killing feature imho to the language…