In this episode, Conor and Bryce chat with Sean Parent about Rust and AI! Link to Episode 252 on Website Discuss this episode, leave a comment, or ask a question (on GitHub) Socials ADSP: The Podcast: Twitter Conor Hoekstra: Twitter | BlueSky | Mastodon Bryce Adelstein Lelbach: Twitter About the Guest: Sean Parent is a senior principal scientist and software architect managing Adobe's Software Technology Lab. Sean first joined Adobe in 1993 working on Photoshop and is one of the creators of Photoshop Mobile, Lightroom Mobile, and Lightroom Web. In 2009 Sean spent a year at Google working on Chrome OS before returning to Adobe. From 1988 through 1993 Sean worked at Apple, where he was part of the system software team that developed the technologies allowing Appleās successful transition to PowerPC. Show Notes Date Recorded: 2025-08-21 Date Released: 2025-09-19 C++ Under the Sea Better code Adobe ASL Adam & Eve Architecture Adobe Software Technology Lab ASL Libraries Rust Programming Language Intro Song Info Miss You by Sarah Jansen https://soundcloud.com/sarahjansenmusic Creative Commons - Attribution 3.0 Unported - CC BY 3.0 Free Download / Stream: http://bit.ly/l-miss-you Music promoted by Audio Library https://youtu.be/iYYxnasvfx8
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.
Transcript
From the show. Tap a time to play from there.
ConorIs this the first time you're writing like production Rust code?
Sean ParentYeah, I'm actually writing Rust code now.
ConorSo what's your experience? I mean, this is this is gonna this could be a very hot news for the orange websites of the world, you know. The C luminary, Sean Perrin's thoughts on working day to day with Rust.
Sean ParentI know, I've got this keynote, and I'm like, yeah, I'm not doing much in C anymore.
BryceTakes on Rust. There's a lot to like. Now are you are you are you writing this Rust code with uh directly or are you using AI?
Sean ParentI am certainly using AI. I mean, one of the great things that I have found with Cursor and Claude, I'm in kind of the Connor camp here. It's it's rocket fuel.
ConorWelcome to ADSP the podcast, episode 252, recorded on August 21st, 2025. My name is Connor, and today with my co-host Bryce, we chat with Sean Parent about Rust and AI. There was an audible sigh from Sean after Bryce uh complaining about Gemini's integration with his email. Feel free to follow up that sigh with uh your thoughts and feelings, Sean.
Sean ParentIt's just the the unpredictable nature of AI.
BryceOh, I we we were just so we were talking about this earlier that I was telling Connor that um I feel like we both are doing the the AI coding thing, and we're both big proponents of it. But I feel like Connor's experience is a lot cheerier where I have what Connor is calling the he Connor's vibe coding, I'm rage coding, where I'm like, oh you stupid robot, why would you do that? And it's like I know it's not a person, but it's still it feels it feels like it's intentionally being incompetent.
BryceIt feels like it's personally, like I feel personally wounded every time it does something uh you know silly. And it's like I can't, I can't overcome this desire to um it's like the worst thing where like it makes a mistake instead of me just being like, all right, I'll just tell it to correct the mistake. I'm like, explain to yourself. You tell me why. Why did you not listen to my instructions?
Sean ParentWell, something I've had reasonably good luck with in cursor is to say you keep doing, you know, X, so please create a prompt for yourself. Uh the rule set, so you will stop. And uh and sometimes it'll create like, you know, I had like a one-sense thing, I told it to stop doing it, and it will create five paragraphs, and it's like, okay, now it works.
ConorLike that's what it took. Wow. What do you call that? Like bootstrapped context engineering?
Sean ParentYou know.
BryceI I tried um I tried something like that where I asked cursor to write a cursor rule for itself. But is it it turns out probably intelligently that they have blocked cursor from writing uh from modifying the cursor roles, which I guess I guess is a sensible thing to do.
Sean ParentYes, it can't it can't modify them, but it can put it in the text that you can then copy and paste into one. So so yeah. Sometimes I'm a little frightened by the lack of guards as it's like, here's this massive mumbo jumbo, execute that in the terminal. And you're like, really? So wait, wait, wait.
ConorActually, I I have a before we start delving uh into the details and weeds, because we haven't talked to Sean in a while. Uh let's well, uh because I'm curious to get you mentioned cursor, but we'll we'll put that uh question on the back burner. The first question, how have you been? We we haven't chatted in a while. I know I think one of the topics we'll get to is uh you are keynoting at C under the C, if I'm not mistaken, which by the time the listeners are listening to this should be in roughly, I think, a month from now, because this will come out in early September. So, anyways, how have you been?
ConorWe'll talk about the upcoming keynote and then and then yeah, we'll take some time. Because I did see that on GitHub, because I follow you, at one point you pushed a commit or a PR that was updating the documentation of something, and it said explicitly in the details, like thanks to Claude or something like that. And I was like, all right, people have been asking to have you back on the pod. Uh, but also we got to get uh you know someone who's a little bit more senior than Bryce and I, their thought on uh, you know, the the age of AI coding. But anyways, how have you been?
Sean ParentUh uh I've been doing well. Yeah. Uh keeping busy. Let's see, probably since last time we talked, I stepped back from managing. So I'm no longer ST Lab manager here. Uh uh, I handed those reins off uh uh to David Senkel.
ConorI s I heard that in a talk that he gave. He said that you like my Jedi mind-tricked him into like giving him what he wanted, but like you also, in order to get what you want, must become manager.
Sean ParentYes, it's uh I've a couple times in my career I've hired my own manager, so so it's worked out well. Yeah. Um uh uh yeah, so I'm I'm coding um and writing. Uh Dave Abrahams and I are working on the book, um, which is moving but slowly. Um this is the better code book. This is the better code book that's you know I announced and and have had a contract with Pearson since 2014, so we're a little more than a decade late.
Sean ParentBut it will happen eventually. I don't know if it will matter at this point because AI is changing everything.
BryceWell, I mean, the the the book might be helpful for the AI, so I know that's that's what Dave and I keep saying.
Sean ParentIt's like okay, you might be writing this for the last reader, right? So that's going along. Uh uh, we also, you know, the the first software technology lab, which was was with uh uh Stepanov and Paul McJones and Matt Marcus and Foster Buritan. Uh one of our big projects uh was a couple of libraries. Um uh the most important one I think was the property model library, which is also known as Atom. Uh it's still kicking around, it's part of ASL out there.
Sean ParentAnd it was always part of a larger vision, which is how do how do we move past imperative coding uh uh uh into a world where we can can can state intense and uh and and have the the system solve for it under the hood. Uh and so property model libraries or property models are um a constrained constraint system uh where you can specify relationships between discrete properties, and then the library will solve for them.
Sean ParentAnd so so it typically gets used for using building UIs where you want to specify constraints and relationships around arguments to some operation, and then you can bind a UI against that model, and then you get a functioning UI. So when you check on this checkbox, that checkbox over there gets disabled. Um, not because there's any code that says when this is on, disable that. It's because the rules around disablement are when an item is either implied by something else in the system or disconnected in the system, it should be disabled.
Sean ParentAnd and so it becomes a much more compact and has a bunch of proofs around it, uh a way to describe uh uh behaviors. So our team has resurrected basically that project and the expanded vision of it as something we call project code less. And uh uh there's a lot of of no-code, low-code systems out there. Um uh, but the vision here is to try to build a low-code environment uh where you describe large systems in terms of intent and and the system constructs from that models and and you get an executing application and do it in a scalable form.
Sean ParentAnd we're we're writing that in Rust. So I've been working on the underlying runtime system for that in Rust.
ConorIt doesn't sound like you're coming, well, you're coming back to the project from uh an idea standpoint, but not from an implementation standpoint. My guess is that the initial iteration of this was in C, and this time you're doing it in Rust.
Sean ParentYeah, the initial implementation of this was in C. And uh, you know, it's been been used at Adobe for 20 years now. Uh, you know, so we have lots of experience with it. And you know, there are some common issues that have come up uh uh around the ergonomics of the system, you know, insights into being able to see uh uh what the actual structure is that gets built for a given given declaration. Uh the previous system was dynamically typed, and uh now there are various act solutions to try to retrofit schemas on top of it so you can verify things at compile time instead of having them fail at runtime.
Sean ParentAnd so then the new system that I'm working on is statically typed and kind of from the ground up and has much better facilities for introspection and much better error reporting. So trying to address all of those those issues. So it's it's uh it's a full rethink and rewrite.
ConorAnd is this the first time you're writing like production Rust code? I imagine you've dabbled in it before, but I don't recall chatting with you saying that, oh yeah, we're doing you've mentioned libraries at Adobe, but I I I thought that was you always were referring to them as a project somewhere else, but it sounds like you're actually writing Rust code now.
Sean ParentYeah, I'm actually writing Rust code now.
ConorSo what's your experience? I mean, this is this is gonna this could be a very hot news for the red the orange websites of the world, you know. The C luminary, Sean Perrin's thoughts on working day to day with Rust.
BryceYou better be careful, they're gonna take away your keynote from uh CPP and C.
Sean ParentI know, I've got this keynote, and I'm like, yeah, I'm not doing much in C anymore, uh, which isn't quite true. I've been spending I spent my morning here working on on C libraries, but um takes on Rust. There's a lot to like. One of the things I really like about uh Rust is the tooling and the setup environment and you know, cargo for doing package management and the fact that uh unit tests are are directly in your source files along with documentation tests and in Cloud or VS Code, you can just click on the test to execute it and uh you know run things directly in your IDE and build your documentation and uh view it.
Sean ParentAnd so all of that is just so much easier to get set up in in cargo. And then from a language standpoint, there's uh a lot to like about it. There's a lot of things they got right. Um destructive move as the default keep allocations are explicit and usually not necessary, so it's not like a reference semantic language, you know, like Python or things like that. So you can write efficient code. Uh they don't have production coroutines, you know, their coroutines are a nightly build. They do have have kind of a partial implementation of coroutines that they use for um async and await.
Sean ParentUh, but even at that level, their coroutines or function objects of that level are just objects, unlike in in uh C, where you get this implied heap allocation and type erasure that goes on with coroutines, and so coroutines become fairly heavyweight. Uh the fact that void, which is just just the uh uh empty tuple in Rust, is regular, um, cleans up so much code. So that's all.
BryceWhat do you what do you not like about Rust? What do you think you say you well, you said that those are the things that you think they're doing right. What are the things you think they're doing wrong?
Sean ParentThere is uh no specialization in in Rust. So if I have a, for example, in C, you get used to this notion of you've got forward iterators and bidirectional iterators and random access iterators, and those each specialize the other one, right? So random iterator is more specialized than just a forward iterator. And if I'm writing an algorithm in terms of uh forward iterators, and I call something that could be done more efficiently if it's a random access iterator, and I happen to have a random access iterator, it will call the specialized function and I'll get the more optimal path.
BryceRust doesn't have this?
Sean ParentRust does not have this.
BryceBut they have like operator overloading, right?
Sean ParentUh they do not have operator overloading directly, they have it through traits, yeah. Um uh uh, which isn't bad. Uh uh uh but the syntax is incredibly verbose. You know, in Rust in general, the syntax is even worse than C, which is unbelievable because C's syntax is so horrible. Uh, you know, but in Rust, it's like, oh, I want to create uh a class, and in C, I could create a class and inline all of my member functions in it.
Sean ParentAnd if I have the right set of member functions, then that might conform to some concept. And uh, you know, the fact that I don't have to declare conformance is problematic in C. Um, uh, but the fact that I can kind of write everything in one unit is nice. And in Rust, I have to say, okay, I've got a struct, and my struct just has data members and no methods on it. And then I have to write a separate block that's an implementation of that struct that provides the the methods on my on my class.
Sean ParentAnd then I want to say, oh, this thing is going to, you know, conform to a trait. Well, I have to say I'm implementing the trait for my class, and then I have to specify how I'm implementing the trait. So it just becomes, you know, a bunch of blocks and very verbose. And the the generic uh syntax is very verbose. And and you know, a lot of people complain about the borrow checker. Honestly, I've never had a problem with the borrow checker, but it's because I write everything in terms of whole part relationships, anyways.
Sean ParentAnd so the borrow checker, when it does come into play, it's just syntactic noise. I just have to say, you know, tick A, tick A, tick A, tick A, which is basically, you know, I'm returning a reference, and the reference is going to be to one of my arguments and because I'm following strict whole part relationships. Or I have to say tick static around a generic type because otherwise it uh wouldn't compile because I'm taking that type out of a scope, and uh Rust has a notion of local type, so you have to say no, no, no, that has to be a global type, so I can basically take it out of scope.
BryceNow, are you are you are you writing this Rust code with uh directly or are you using AI?
Sean ParentI am certainly using AI. I mean, one of the great things that I have found with Cursor and Claude, I'm in kind of the Connor camp here. It's it's rocket fuel. And for learning a new system, uh uh, you know, I can ask, uh, you know, okay, here's what I want to do. How do I do that? And it will give me a block of Rust code. Now, if I don't understand that Rust code immediately, then I will go and ask questions like why are you doing it this way? And uh and then I will usually double check that information in part because I got burned badly once, because the I asked a question about uh uh if a tuple in Rust, like let's say I had a tuple of A, B, and then I I had another tuple that was A, B, comma, C.
Sean ParentThe question was is there a guarantee in Rust that the prefix A B has the same layout between those two tuples? And since I was doing a uh a bit of type erasure and a bit of unsafe code in inside of Rust, uh the answer to that question was very important. Yeah. And uh, I believe it was Claude, uh gave me a very beautiful answer about why that was guaranteed with logic and links, and and uh, you know, it started with, well, it's not explicitly stated in the standard, but it it must be true because, you know, A, B, C, D, E.
Sean ParentUh very well reasoned, very nice. And so I took that at face value and uh uh implemented my code accordingly. And two weeks later, I had a really hard bug to track down, and it uh uh took me a solid week, because it's you know a memory stomper, um, uh, you know, in unsafe code, uh, to hunt down what was going wrong. And it turns out that that is not a true statement. Those layouts are are explicitly not guaranteed to match, they just happen to usually match, and so I got away with it.
Sean ParentUm uh and I went back to my tab with the with the proof and actually clicked on all the links, and half of them went nowhere. And this is just total hallucination bullshit. Um uh uh so uh so after that experience, I'm a bit more cautious with just accepting things at face value.
BryceYeah, I never I never trust it. I never trust it.
ConorDo you remember what uh was it 3.5, 3.7, 4.0?
Sean ParentProbably 3.5. It was before 4.0. Um certainly 4.0 has been nicer. Uh I still think uh uh Cloud 4.0, I still think does a better job than GPT 5, although the one thing I do like about GPT-5 is it doesn't blow so much smoke at you, right? Right. Cloud 4.0 is like, hey, that's a great question.
BryceYeah.
Sean ParentUh uh no matter what you ask, right? Right, right. It's always like that's a great insight. Let me go munge all of your code with that great insight. And it's like, no, that was a horrible insight.
BryceAnd I'm almost afraid to ask it questions that I like. I'm almost afraid to ask it questions or make suggestions because it's like I know that it's gonna be like, oh, like I wanna make the user happy, so I'm I I won't tell them no. I'll just do whatever they suggest.
Sean ParentYeah, yeah. And GPK5 doesn't tell you no, but it doesn't compliment you for your incompetence. Um the one feature I really, really, really want in these AI systems is for them to be competent enough, you know, if I say, hey, how about you do it this way, to go to go, well, that's a pretty stupid request because that way, you know, it would contradict these other things that you said you wanted, or it would just make a mess, or for whatever reason, right?
Sean ParentBut it will never tell you no.
ConorI've only just realized now that maybe this is a skill that I have honed for different reasons than coding, is that uh my fiance, uh Shima, and I constantly like if we uh disagree on some kind of factual thing or whatever, uh she'll be like, well, let's just ask, you know, ChatGPT. And I'll be like, and uh it at first I'd be like, sure. A month later of that, I'd be like, no, sweetie, uh like I'm gonna ask the question because you load your question. Like you're so loaded. You put the answer that you want in your question. And and then she's like, no, I don't.
ConorAnd I was like, all right, well, ask it the opposite of what you said, and then oh, I don't want to ask it that, because then, you know, so it's there are ways where if you know there's uncertainty, uh, like you don't know if this is a good or bad idea. I will explicitly be like, hey, I'm looking for suggestions on how to architect this little piece. Like, give me five different things and and tell me what you think the best is. Whereas if you already have, like, oh, maybe this is good, but I don't know, and then you ask it, is it this good a day, uh, this a good idea, it'll be like, sure, you can implement it like this, even if it's completely wrong. And uh I've never realized that that maybe is something I'm secretly or like silently doing, um, and that it's like a it's a hone skill of like how to ask the question based on your confidence level of of what you're looking for.
Sean ParentYeah. And I mean, certainly if I'm not, if I'm confused, right, right, and I know I'm confused, then I will try to say, say something like, you know, don't change any of my code. Here's the problem I'm trying to solve. Yeah. Give me three suggestions on the on an approach. Right, right. Uh, and that can be really useful. But it's the times where where I'm like, like, oh, I want to just add this feature, so please just add this feature. And it's like, sure. And it just destroys all of my code and uh, you know, generates a bunch of errors, and it's like, oh, well, let me go fix those errors.
Sean ParentWell, now that unit test is failed. Let me just remove that unit test. And it just goes off. And it's like, okay, how about you just say say, you know, I could do that, but yeah.
BryceI've I've played around with like rules to tell it like, don't like the two, my two biggest gripes are when it makes when it makes uh when changes are made that were not things the thing that I explicitly requested. Like I asked it to do X and it noticed something else, and it went to try to do that other thing too. And it's like, no, I told you to do this, just stick with that. And then the second thing is freaking comments. It adds so many comments, and most of them are low quality comments. So I almost I almost always when I'm asking it to do stuff, like the last sentence I'll write is like no comments.
Sean ParentSo my uh yeah, an annoying thing I hit the other day is it's it's uh uh I had it refactor a file into a separate library and put it in in a separate library, and I wanted it all set up with doxygen and stuff, C library to to to build the documentation. And uh so it does it all, and I look and the documentation is empty. And I'm like, I'm like, oh why is this, right? Because I had all of in the source file, I had all of the doc inline doxygen comments, and uh I go and I look at the source file, and all of the doxygen comments are stripped, and it's just got one non-doxygen comment that says this file was was moved from this other other library.
Sean ParentI'm like, No.
BryceI I found that I found that for some tasks like that, if you ask it like when you're asking it to refactor code, um if you ask it like, hey, like move this file, like this like I was trying to merge two libraries together, a similar thing. Um and asking it like just take the functions from this thing and put it into this other thing, that was really tough for it. Um whereas like for me, it was very easy for me to copy and paste all the functions and dump them into the file and then ask it to refactor it.
BryceBut I think that what happens is when you ask it to like move code from one place to another, like it it doesn't, at least some of them don't have like a native tool for doing that. And so what it means is that the way that it's moving the code is it gobbles it up in the context and then it spits it out in the output. And that means that your code is going through, going through the network, and that stuff might happen to it when it does.
Sean ParentYeah, it's like it's like, oh, let me read this code and now let me try to recite it from memory.
BryceYes.
ConorYeah. Be sure to check these show notes either in your podcast app or at adspthepodcast.com for links to anything we mentioned in today's episode, as well as a link to a GitHub discussion where you can leave thoughts, comments, and questions. Thanks for listening. We hope you enjoyed and have a great day.
BryceLow quality, high quality. That is the tagline of our podcast.
ConorThat's not the tagline. Our tagline is chaos with sprinkles of information.
In this episode, Conor and Bryce chat with Zach Laine about C++26 Reflection vs CRTP, AI, kids & more. Link to Episode 313 on Website Discuss this episode, leave a comment, or ask a question (on GitHub) Socials ADSP:...
In this episode, Conor and Bryce chat with Zach Laine about the C++26 contracts fiasco. Link to Episode 312 on Website Discuss this episode, leave a comment, or ask a question (on GitHub) Socials ADSP: The Podcast:...
In this episode, Conor and Bryce talk with Zach Laine about his career and the career changes he has made. Link to Episode 311 on Website Discuss this episode, leave a comment, or ask a question (on GitHub) Socials...
In this episode, Conor and Bryce talk about Bryce's next chapter and where he is leaving NVIDIA for. Link to Episode 310 on Website Discuss this episode, leave a comment, or ask a question (on GitHub) Socials ADSP: The...
In this episode, Conor and Ben chat with Jason Turner about default construction in C++. Link to Episode 309 on Website Discuss this episode, leave a comment, or ask a question (on GitHub) Socials ADSP: The Podcast:...