Adam Leventhal
👤 SpeakerAppearances Over Time
Podcast Appearances
I looked for it, published in Taiwan, all written in Chinese. So I'm not sure I'm the target demo for that. I think the first volume he released a while ago, because he referenced it in his interview with Jensen Wong in the Computer History Museum, Oral Histories. And that was a while ago. But he just released the second volume, which is like 1,200 pages or something like that.
There are no translations of either volume.
There are no translations of either volume.
I mean, am I going to, no, no, he, he, he speaks great English. Like, have you, have you watched the, uh, the episode, the, um, computer history museum interview with Jensen?
I mean, am I going to, no, no, he, he, he speaks great English. Like, have you, have you watched the, uh, the episode, the, um, computer history museum interview with Jensen?
Oh, yeah, because they're listening. They're like, look, I'm just waiting for them to mention my name so I can respond to that invitation. It's been sitting in my inbox.
Oh, yeah, because they're listening. They're like, look, I'm just waiting for them to mention my name so I can respond to that invitation. It's been sitting in my inbox.
Yes. That feels like, you're right, because he's trying to sell his book in English and everything. Yeah, that's right. As opposed to Mars Chang, not trying to sell a book in English.
Yes. That feels like, you're right, because he's trying to sell his book in English and everything. Yeah, that's right. As opposed to Mars Chang, not trying to sell a book in English.
Yeah, look, you can find all the reasons you want for why it can't happen.
Yeah, look, you can find all the reasons you want for why it can't happen.
I have two self-destructive hobbies related to async cancellation. First, I buy all the new books that come out about async rust, and I don't review them because I think it would be rude to. Interesting, because they don't talk about this issue. Oh, because... Okay, as long as they're not listening right now. Because they're all terrible. They're all just like, makes me cry.
I have two self-destructive hobbies related to async cancellation. First, I buy all the new books that come out about async rust, and I don't review them because I think it would be rude to. Interesting, because they don't talk about this issue. Oh, because... Okay, as long as they're not listening right now. Because they're all terrible. They're all just like, makes me cry.
Because it's not even that. It's like, man, the one I got recently, it's like talking about how processes are kind of like threads, but different. It's like, please stop. Please stop. Yeah, exactly. If you're going to talk about a framework which is inherently about concurrency, I'd like you to have a strong understanding about the distinction between what is a process and what is a threat.
Because it's not even that. It's like, man, the one I got recently, it's like talking about how processes are kind of like threads, but different. It's like, please stop. Please stop. Yeah, exactly. If you're going to talk about a framework which is inherently about concurrency, I'd like you to have a strong understanding about the distinction between what is a process and what is a threat.
The other self-destructive habit I have is occasionally attending the Rust Async Working Group meetings. Wow. It's a cry for help, is what I'm saying.
The other self-destructive habit I have is occasionally attending the Rust Async Working Group meetings. Wow. It's a cry for help, is what I'm saying.
um very little like very little not that much and then when i'm there i i offer like unhelpful pedestrian statements like it would be nice if the documentation were better or yeah or like if you could debug the thing that would be nifty and they're like this is great like practical you know salt of the earth kind of feedback but nothing really happens All right. So are we, we'll do it.