4 ms·

Mine is Zig.

by pron 7y ago

Mine is Zig.

dgellow 7y ago
Zig is still very experimental though, the language isn’t stable yet
- AnIdiotOnTheNet 7y ago
  Definitely. However I will say that Zig does so many things right already that I struggle to code in more mature languages without thinking "I wish I was writing Zig right now" all the time.
- pron 7y ago
  True, but I'm not in a hurry. We've waited a long time for a C/C++ alternative, we can wait a bit more. Some find it in D, some find it in Rust, some (like me) are waiting for Zig, and some for something else.
logicchains 7y ago
Are you aware of anyone with large projects in Zig? I'm curious how fast it compiles, given in my view faster compilation is one of the biggest advantages of D over C++ and Rust, due to it having a lightweight compiler, DMD. Zig seems to still use LLVM, like Rust, which is relatively slow.
- drfuchs 7y ago
  In his live-stream three days ago, Andrew Kelley showed the beginnings of Zig directly generating debug-mode executables, very quickly. And that’s before incremental compilation and linking. This guy is amazing. https://www.twitch.tv/videos/602715503 https://www.twitch.tv/videos/602715503 [edit: at 10:20]
  - logicchains 7y ago
    Ah, that's awesome! Really cool to see a new language taking compile-time so seriously.
    - setpatchaddress 7y ago
      Fast compile time isn't actually that hard for a C-like language. Good code optimization and fast compile time is hard.
      - alexhutcheson 7y ago
        Fast compile time on large projects is really hard for C and C-compatible languages due to the preprocessor and #include. Not an issue if you're comparing compilation for a single file, but it turns into a substantial fraction if your compile time when that file transitively #includes 10s or 100s of headers.
smallstepforman 7y ago
Andrew needs to radically change his stance on Tabs for the language to be taken seriously. White space must be ignored, and Andrew should overlook his personal bias and cater to the ‘preserve white space’ crowd. Because formatting and readability matter - a lot.
- schaefer 7y ago
  You refer to "Andrew's stance on tabs" without being specific or providing a reference, so I wend digging for more details in the language FAQ. From the reference I found[1], Andrew's stance is: The current zig tooling forces spaces instead of tabs because the tooling for the language is not yet complete. The self hosted compiler (which the community will start using just as soon as it's ready) already does accept both tabs and spaces. So, I'm not able to understand your complaint at all. Perhaps you could you elaborate, provide a reference, or soften your stance? [1]: https://github.com/ziglang/zig/wiki/FAQ#why-does-zig-force-me-to-use-spaces-instead-of-tabs https://github.com/ziglang/zig/wiki/FAQ#why-does-zig-force-m...
  - saagarjha 7y ago
    I am very curious why the stage1 compiler cannot just run zig fmt prior to parsing the code as a stopgap until the self-hosted compiler is complete…

Mine is Zig.

by pron 7y ago

Mine is Zig.

dgellow 7y ago

Zig is still very experimental though, the language isn’t stable yet

AnIdiotOnTheNet 7y ago
Definitely. However I will say that Zig does so many things right already that I struggle to code in more mature languages without thinking "I wish I was writing Zig right now" all the time.
pron 7y ago
True, but I'm not in a hurry. We've waited a long time for a C/C++ alternative, we can wait a bit more. Some find it in D, some find it in Rust, some (like me) are waiting for Zig, and some for something else.

logicchains 7y ago

Are you aware of anyone with large projects in Zig? I'm curious how fast it compiles, given in my view faster compilation is one of the biggest advantages of D over C++ and Rust, due to it having a lightweight compiler, DMD. Zig seems to still use LLVM, like Rust, which is relatively slow.

drfuchs 7y ago
In his live-stream three days ago, Andrew Kelley showed the beginnings of Zig directly generating debug-mode executables, very quickly. And that’s before incremental compilation and linking. This guy is amazing. https://www.twitch.tv/videos/602715503 https://www.twitch.tv/videos/602715503 [edit: at 10:20]
- logicchains 7y ago
  Ah, that's awesome! Really cool to see a new language taking compile-time so seriously.
  - setpatchaddress 7y ago
    Fast compile time isn't actually that hard for a C-like language. Good code optimization and fast compile time is hard.
    - alexhutcheson 7y ago
      Fast compile time on large projects is really hard for C and C-compatible languages due to the preprocessor and #include. Not an issue if you're comparing compilation for a single file, but it turns into a substantial fraction if your compile time when that file transitively #includes 10s or 100s of headers.

smallstepforman 7y ago

Andrew needs to radically change his stance on Tabs for the language to be taken seriously. White space must be ignored, and Andrew should overlook his personal bias and cater to the ‘preserve white space’ crowd. Because formatting and readability matter - a lot.

schaefer 7y ago
You refer to "Andrew's stance on tabs" without being specific or providing a reference, so I wend digging for more details in the language FAQ. From the reference I found[1], Andrew's stance is: The current zig tooling forces spaces instead of tabs because the tooling for the language is not yet complete. The self hosted compiler (which the community will start using just as soon as it's ready) already does accept both tabs and spaces. So, I'm not able to understand your complaint at all. Perhaps you could you elaborate, provide a reference, or soften your stance? [1]: https://github.com/ziglang/zig/wiki/FAQ#why-does-zig-force-me-to-use-spaces-instead-of-tabs https://github.com/ziglang/zig/wiki/FAQ#why-does-zig-force-m...
- saagarjha 7y ago
  I am very curious why the stage1 compiler cannot just run zig fmt prior to parsing the code as a stopgap until the self-hosted compiler is complete…