Did Zig Fix Async / Await?
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Related videos
Why Did They Build This?
The PrimeTime
126.3k views
Zig is at a crossroads
The PrimeTime
120.3k views
It's all fake
The PrimeTime
88.9k views
I Watched It
ThePrimeTime
210.0k views
We did it?
ThePrimeTime
102.6k views
Final stretch
ThePrimeTime
34.3k views
Zig and Rust in Production (ft. Matklad)
ThePrimeTime
93.2k views
AI Skeptic Friends
ThePrimeTime
344.3k views
Experts Have It Easy...
ThePrimeTime
96.5k views
C Must Die
ThePrimeTime
222.3k views
Top Comments (10)
25:07 I feel like people will be forgiving of it for quite a long time because 1) it's very explicitly not anywhere near 1.0 2) It's very easy to manage several zig compilers, so it's not that hard to compile ,with old compiler until you know the better way 3) Ziglang people are generally people who are very eager to learn new stuff(duh)
Dont' rush zig. I mean look at the amount of alphas cosmic desktop has and is going through, and people still use and look forward to it... And those users are less okay with their DE breaking than a dev who's chosen to write something in zig... if the dev wants to cry about a breaking change in zig, they'd likely not have used it to begin with
I am c programmer for more than 30 years and I love c, but I really like zig too ... Let us see where zig is going ...I think that the zig developers should resist the wish stabilizing zig soon and keep experimenting especially with consistent naming and syntax schemes, so that we get finally a very solid and understandable tool in our hand
At first I was confused by the IO name for this interface, but I actually think it makes a lot of sense. My biggest complaint about Rust's async is that the actual IO operations you do in a library lock that library to a specific runtime which locks consuming code into that runtime. For example, if you have a library that makes HTTP requests using a tokio::TcpStream, now any code that brings in this library must run the library inside a Tokio event loop. If the consumer wanted to use async-std or embassy for embedded, that library is unusable for the use case. The Zig IO interface seems to remedy this problem by not only standardizing the state machine interface (Rust's Future type), but also the interactions with the system around the running code. The IO interface is basically a language provided sans-io system. Disclaimer: I've never written a single line of Zig, but I really love this concept and want to see it come to fruition.
I'm a Rust fanboi but damn is this some amazing stuff that Andrew is cooking up. Zig continues to amaze me
19:48 zig has literally the best casting I have ever seen it even enforces pointer alignment which rust does not. This makes zig casting a lot safer also.
24:20 - "I'm not smart, I just try a lot and never settle for something that's not perfect." - What a sentiment!
still learning rust the hard way at a veryyyyy slowwwww pace. I tried to write a few stuffs in Zig last year just to see what it was, seems pretty impressive for such a young language. Yet the documentation was a bit scarce, but it seems to improve quite fast. Kudos to the community and incredible work from Andrew, the "one man operation" who has been beyond that.
Its funny how Prime is using javascript as a shorthand way to explain programming concepts. Like, he knows that most people out there are Javascript Andys
Honestly? As someone who loves Zig, I'm more than fine with the language changing a lot like that. The Zig team isn't afraid to experiment, to try something new, and I love it.
Unlock the Data Inside
Turn Videos into Knowledge
- Get FREE 10/day: transcripts, summaries, chats
- Chat with videos, export text & PDF
- $1 free API credit for RAG, chatbots & research
Free forever plan • All features unlocked
Top Comments (10)
25:07 I feel like people will be forgiving of it for quite a long time because 1) it's very explicitly not anywhere near 1.0 2) It's very easy to manage several zig compilers, so it's not that hard to compile ,with old compiler until you know the better way 3) Ziglang people are generally people who are very eager to learn new stuff(duh)
Dont' rush zig. I mean look at the amount of alphas cosmic desktop has and is going through, and people still use and look forward to it... And those users are less okay with their DE breaking than a dev who's chosen to write something in zig... if the dev wants to cry about a breaking change in zig, they'd likely not have used it to begin with
I am c programmer for more than 30 years and I love c, but I really like zig too ... Let us see where zig is going ...I think that the zig developers should resist the wish stabilizing zig soon and keep experimenting especially with consistent naming and syntax schemes, so that we get finally a very solid and understandable tool in our hand
At first I was confused by the IO name for this interface, but I actually think it makes a lot of sense. My biggest complaint about Rust's async is that the actual IO operations you do in a library lock that library to a specific runtime which locks consuming code into that runtime. For example, if you have a library that makes HTTP requests using a tokio::TcpStream, now any code that brings in this library must run the library inside a Tokio event loop. If the consumer wanted to use async-std or embassy for embedded, that library is unusable for the use case. The Zig IO interface seems to remedy this problem by not only standardizing the state machine interface (Rust's Future type), but also the interactions with the system around the running code. The IO interface is basically a language provided sans-io system. Disclaimer: I've never written a single line of Zig, but I really love this concept and want to see it come to fruition.
I'm a Rust fanboi but damn is this some amazing stuff that Andrew is cooking up. Zig continues to amaze me
19:48 zig has literally the best casting I have ever seen it even enforces pointer alignment which rust does not. This makes zig casting a lot safer also.
24:20 - "I'm not smart, I just try a lot and never settle for something that's not perfect." - What a sentiment!
still learning rust the hard way at a veryyyyy slowwwww pace. I tried to write a few stuffs in Zig last year just to see what it was, seems pretty impressive for such a young language. Yet the documentation was a bit scarce, but it seems to improve quite fast. Kudos to the community and incredible work from Andrew, the "one man operation" who has been beyond that.
Its funny how Prime is using javascript as a shorthand way to explain programming concepts. Like, he knows that most people out there are Javascript Andys
Honestly? As someone who loves Zig, I'm more than fine with the language changing a lot like that. The Zig team isn't afraid to experiment, to try something new, and I love it.