Why he is not ready : > comptime feels like a hack, I much would prefer the legacy preprocessor macros C if I can’t have generics. If comptime is a hack, the

Why he is not ready : > comptime feels like a hack, I much would prefer the legacy preprocessor macros C if I can’t have generics. If comptime is a hack, the preprocessor is the king of hacks. > You still end up chasing SIGSEGV Don't the zig compiler in safe mode tell you about it ? Sure it's not as good as preventing a entire class of error but at least you probably get the line in your code where it happens. If you are used to C as you say you are, and if you think Zig's purpose is to work alongside/replace C as you say you think, well, that's not something to be held against zig adoption. > You end up leaking memory But he also says "Of course, Zig has really nice tooling here to catch them quickly, so perhaps not such a big issue." So nothing to see here. All the rest is how zig/its ecosystem/industry/community is not there yet which, of course, it's not 1.0 yet. From the zig website : "Zig is immature. Even with Zig 0.13.0, working on a non-trivial project using Zig will likely require participating in the development process." I don't blame the author but that's not really Hn worthy nor newsworthy