I didn’t really like any of them, so I wrote my own :)
I wanted the compiler to automatically parallelise and vectorise my code, because CPUs these days are inherently multicore, and not using the GPGPU seems like a huge waste of resources, so: xc[1]
Structured closely to “C with classes”, but has blocks/callbacks as fundamental types and implements ARC to make memory management pretty trivial. Allows 3rd-party libraries without header files by reading the DWARF content of the library, does the auto-detection of data-parallel code etc etc. Docs at the link.
Very good build tooling was huge plus, but now with llm this is not a differentiator anymore.
With strict c compiler flags, and other sanitizer tools many of the niceties of zig can be solved - maybe not all.
Two big items -- RAII, and memory safety -- neither Zig, not C solves them. Rust does.
So, I would choose C or Rust based on the needs.
Also, if someone here have a compelling reason as to when/why Zig is useful in professional grade projects, where the language has to scale to large codebases, I would like to hear it.
Pascal for me. The case sensitivity and inscruitible variable and type syntax of C/C++ don't match the way I think. Then there's all the macros and .h files.
C ofcourse :). its incredibly portable and gives you full control over thats happening under the hood. I dont know enough Rust and Zig but C has stood the test of time for a reason.
I'm trying rust for now; start from C/C++ then switched for Java for many years; and looks people are talking with Rust so I want to give it a try ;)
To be frank, does it matter in the AI vibe coding era? so long you can understand the program, although in a unfamiliar language, but you can read and write in C!!
finally, zig users enter the thread.
i come from/currently use c, but i do enjoy zig. rust, not so much but i like to think i at least know my way around the rust language.
I wanted the compiler to automatically parallelise and vectorise my code, because CPUs these days are inherently multicore, and not using the GPGPU seems like a huge waste of resources, so: xc[1]
Structured closely to “C with classes”, but has blocks/callbacks as fundamental types and implements ARC to make memory management pretty trivial. Allows 3rd-party libraries without header files by reading the DWARF content of the library, does the auto-detection of data-parallel code etc etc. Docs at the link.
1: https://compile-xc.org/
Very good build tooling was huge plus, but now with llm this is not a differentiator anymore.
With strict c compiler flags, and other sanitizer tools many of the niceties of zig can be solved - maybe not all.
Two big items -- RAII, and memory safety -- neither Zig, not C solves them. Rust does.
So, I would choose C or Rust based on the needs.
Also, if someone here have a compelling reason as to when/why Zig is useful in professional grade projects, where the language has to scale to large codebases, I would like to hear it.
It’s something I still believe, even now, in the age of AI.
But also C and Python. :)
I love how easy it's to write system level tests in Python.
To be frank, does it matter in the AI vibe coding era? so long you can understand the program, although in a unfamiliar language, but you can read and write in C!!
And my favourite flavour of ice cream is vanilla.