←back to thread

42 points tosh | 4 comments | | HN request time: 0.629s | source
1. thomascountz ◴[] No.46186897[source]
I just nearly finish Ziglings and it's great! Though the skipped exercises around async is confusing as a newcomer. From the Codberg issues and PRs, it seems like perhaps an update is in the works. Otherwise, I learned a lot and would recommend it!
replies(2): >>46187578 #>>46192918 #
2. naikrovek ◴[] No.46187578[source]
async/await is confusing in every language it is implemented in. Whoever came up with this paradigm has (or at the time, had) zero idea about usability. It is the programming equivalent of the programmer user interface. Makes perfect sense to the one person because they wrote it; it’s an enormous pain for everyone else.

Raw threads and doing everything manually makes far more sense to me.

And of course Goroutines in Go make the most sense but they’re not as performant as something like Zig by any means.

3. dardeaup ◴[] No.46192918[source]
I've been holding off on Zig because it hasn't reached 1.0 milestone, but I'm starting to think that it might be time to start digging in. Is Ziglings kept up with language changes being made in Zig? It would be very frustrating to find that Ziglings is out of sync with the newer version of Zig that you might be using at the time.
replies(1): >>46197378 #
4. hiccuphippo ◴[] No.46197378[source]
It uses the development version so it keeps in sync. I don't think we'll see many changes in the language itself before 1.0, they are no longer accepting changes to it. Most changes from now on will be in the Standard Library.