3 ms·

Zig is promising. The UX problem that the author talks about will be solves by Zig. About documentation, its still not 1.0, the language. So, its a work in pro

Zig is promising. The UX problem that the author talks about will be solves by Zig. About documentation, its still not 1.0, the language. So, its a work in progress.

tails4e 6y ago
I'm curious about this. It seemed to be alot of 'work' just to get arguments. While I could read the code with no prior experience, there were enough unexpectedly verbos things in there that suggested it could take a considerable time to learn
- himujjal 6y ago
  No task is too easy. For easy, we need to jump down to Python. Even C is too easy to learn but difficult to write. Zig is kind of in between Go and Rust in terms of the learning curve. In terms of programming, it is in between C and Rust. But it is simple enough. The documentation as I said for the stdlib isnt that great right now as I said.
  - dnautics 6y ago
    While I agree that Zig is in between Go and Rust, you're gonna find a lot of crazy stuff that will tie your brain in knots with Go. A few examples: - Json parsing being special cased into the language - multiplying a user-input integer with a time value to be a timeout - channels and goroutines (sorry, I've been spoiled by erlang) Aside from things that are actually bugs, I haven't found anything like this in Zig. On the contrary, I typically have found something that doesn't work how I expect, and then I think about it, and it's "of course it's like this, why isn't C like this??".
  - tails4e 6y ago
    I found the cxx example very easy to read, which surprised me, it was not thst verbose. The D example another poster has in this thread was the easiest and cleanest IMHO.
- lhorie 6y ago
  IIRC there's a std.os.args or some such that is just a slice of byte arrays in unix platforms. The iterator API builds cross-platform support on top of it, as I understand. In my books, that's acceptable for an actually-low-level language.

Zig is promising. The UX problem that the author talks about will be solves by Zig. About documentation, its still not 1.0, the language. So, its a work in progress.

tails4e 6y ago

I'm curious about this. It seemed to be alot of 'work' just to get arguments. While I could read the code with no prior experience, there were enough unexpectedly verbos things in there that suggested it could take a considerable time to learn

himujjal 6y ago
No task is too easy. For easy, we need to jump down to Python. Even C is too easy to learn but difficult to write. Zig is kind of in between Go and Rust in terms of the learning curve. In terms of programming, it is in between C and Rust. But it is simple enough. The documentation as I said for the stdlib isnt that great right now as I said.
- dnautics 6y ago
  While I agree that Zig is in between Go and Rust, you're gonna find a lot of crazy stuff that will tie your brain in knots with Go. A few examples: - Json parsing being special cased into the language - multiplying a user-input integer with a time value to be a timeout - channels and goroutines (sorry, I've been spoiled by erlang) Aside from things that are actually bugs, I haven't found anything like this in Zig. On the contrary, I typically have found something that doesn't work how I expect, and then I think about it, and it's "of course it's like this, why isn't C like this??".
- tails4e 6y ago
  I found the cxx example very easy to read, which surprised me, it was not thst verbose. The D example another poster has in this thread was the easiest and cleanest IMHO.
lhorie 6y ago
IIRC there's a std.os.args or some such that is just a slice of byte arrays in unix platforms. The iterator API builds cross-platform support on top of it, as I understand. In my books, that's acceptable for an actually-low-level language.