Comments by "Loris Cro" (@kristoff-it) on "Developer Voices" channel.

  1. tigerbeetle, ghostty, bunjs are the major ones
    5
  2.  @dmitriidemenev5258  it's not bad, it just doesn't work if you try to cross-compile. With Zig it works, easy as that.
    4
  3. Almost, Go's defer runs at the end of the function, Zig's runs at the end of the enclosing scope.
    3
  4. nope
    3
  5. Go used to work like that but then all Go programs broke when apple changed the syscall interface. On macOS, FreeBSD and Windows you have to use the system libc as that's the stable interface.
    3
  6. Zig is a non profit with zero ties to big tech. We only have the money to pay devs & more importantly our finances are public (legally have to be). You might want to re-calibrate your opinions :^)-
    3
  7. musl is a libc though :^) no_std is good but that takes away a good chunk of the stdlib, which is significantly different than how things work in Zig
    2
  8. The cc crate invokes the system C compiler.
    2
  9. The upcoming optimizing backend for Zig is going to be tailored for Zig. LLVM is meant to be much more general-purpose.
    2
  10. Zig can link against libc, it just doesn't do so by default on platforms that don't require you to do that (mainly Linux). On other platforms, eg macOS, it will link every time. IIRC OpenBSD isn't a Tier 1 supported target yet so you might encounter some annoyances but Zig can play nice with that kind of system.
    2
  11. If you have to wrangle C/C++ projects (improve their build system, incrementally port them to a new language, etc), Zig is the best tool for the job past a certain level of complexity (Odin can link to C libs). If you need runtime type information, Odin will have it, Zig won't. Past that it's a matter of preference.
    2
  12. Here's one: Zig is better than C/C++ toolchains at building C/C++ code :^)
    2
  13.  @zachend2750  The main point is that it's factually false to claim that Go doesn't depend on any libc. If the OS declares that to be the public interface, that's what you have to use, otherwise all programs written in your language will break at random points in time (including when the OS releases a new patch version, eg v11.0.1), which is clearly undesirable.
    2
  14. the build system is entirely part of the zig standard library, see lib/src/Build.zig, everything is defined in there, also the Learn section on the official Zig website has a build system guide
    1
  15. I gave a talk titled "Deinventing The Wheel" (it's available on youtube) about the limits of wheels. If you can be confident it will work reliably, there's a lot to like about building software precisely for the exact set of instructions that your machine support.
    1