Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

ADSP: Algorithms + Data Structures = Programs

ADSP: Algorithms + Data Structures = Programs artwork

Episode 98: The Future of C++ with Sean Baxter (Part 2)

Oct 7, 202230 minAudio
ShareXLinkedInFacebookWhatsAppEmail

In this episode, Bryce and Conor continue their interview with Sean Baxter about all of the C++ successor languages. Link to Episode 98 on Website Twitter ADSP: The Podcast Conor Hoekstra Bryce Adelstein Lelbach About the Guest: Sean Baxter is an independent programmer and the author of Circle, the next-gen C++ compiler. He formerly worked at DE Shaw Research, NVIDIA and JPL. Show Notes Date Recorded: 2022-09-25 Date Released: 2022-10-07 Sean Baxter on Twitter Sean Baxter cpp.chat Episode Sean Baxter CppCast Episode Circle Compiler Val Programming Language Jakt Programming Language Circle Metaprogramming: Better Features Make Better Libraries - Sean Baxter - CppNow 2022 Carbon Language: An experimental successor to C++ - Chandler Carruth - CppNorth 2022 Carbon Programming Language CppFront CppCon Keynote about CppFront: Can C++ be 10x Simpler & Safer? - Herb Sutter - CppCon 2022 CppFront Reddit Thread Swift Programming Langauge Rust Programming Language Arthur Whitney Python Language Summit 2022 The C++0x “Concepts” Effort Swift Protocols Rust Traits Carbon Interfaces C++20 Concepts 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.

Herb Sutter (Clip)I would like to encourage us, as a community of 7 million C ⁇ developers around the world, as we consider C ⁇ 's future, to push the boundaries to bring C ⁇ itself forward and double down on C ⁇ , not be quick to switch to something else.

ConorWelcome to ADSP the podcast, episode 98, recorded on September 25th, 2022. My name is Connor, and today with my co-host Bright, we continue our conversation with John Baxter about the future of C and all of the C successor project. What do you think of that? And like also like if you had a crystal ball or you had to bet, you know, five, ten years from now, what do you think the low-level language space is gonna? Is everyone gonna be writing in circle? Is it gonna be C ⁇ is just gonna be in slow decline?

Sean BaxterI mean, I'm my whole adult life has been C ⁇ . And I don't want to learn a new language just because other people say I should learn it, or because other people say it's better. I am I feel confident in C. It can express my intent and we can make it better. And also, like, I'm there's um another million people who have been using this language successfully, with some frustration, sure, but they've built the whole modern world out of C ⁇ .

Sean BaxterAnd I think we're gonna keep with this language. We should make it better, and we should we should kind of honor this multi-billion dollar software investment that's been built up over decades. And I think the the future will look, hopefully, like like the today looks, just with a better a better language. I mean I I just don't see everyone jumping to to Rust and then putting these huge, complicated source bases in jeopardy. They say Rust is safer, but not when you have to rewrite everything you already have.

BryceI I think I I agree with Sean and I I think I think our biggest problem is our evolution process, and I think that if we can if we can improve our evolution process, and and if we can if we can develop the willpower to make C ⁇ a better language, I'm I'm confident that we can do so. Um I I I do not believe that there are fundamental uh technical challenges that that cannot be overcome here.

BryceUm I I think we could move two, three, four, five times faster um if uh if we had a better evolution model. Um and you know not everybody's gonna necessarily be hap happy about um uh what moving faster would look like. Um and it would mean I think everybody would have to make some compromises.

BryceUm but I I think that it's it's doable. I I do think that if anything dooms the language, it would be that. Um but I don't think C is going anywhere. Um I just don't want to see it go the route of um uh uh you know, a COBOL or a Fortran, where it's uh uh a language that's uh very important, um used in a lot of places, but increasingly hard to find um uh younger engineers who are interested in because it's uh not kept up with the times.

Sean BaxterYeah. I think any language you can imagine, I think we can really get there from C. And and I think maybe that's the shortest line, even. Because um it's so hard to generate new user base. Yeah. Apple could do it with Swift because like he had to buy into their whole like Objective C slash Swift framework drawings. They have a kind of a walled garden. But yeah, for everyone else, like if you start with C user base, man, what a what like an amazing amount of momentum you have once.

BryceYeah, and it's not just the user base, it's the ecosystem too. It's like it's like an inertia is is king in software. Like if you have something that has inertia.

Sean BaxterI think momentum, you should say momentum.

BryceMomentum?

Sean BaxterI mean, inertia's kind of got like negative connotations, but Okay, alright.

BryceBut momentum is key in software. Um and and I I I just like everything that I've seen in my career tells me that. Everything I've seen in my career tells me that it's better to try and incrementally improve what you have in front of you instead of rewriting it all from scratch. I I get that the rewriting it all from scratch has worked for Arthur Whitney. And I and I I certainly I get that there's times when that is the right thing to do, but the the cost for that is so high, especially when you've got an ecosystem and a and a developer base um out there, when it's something that's a community project and that um uh it you know rebuilding that community um or moving that community, um, especially when the size of C ⁇ is just so much effort and so much work.

BryceWhereas just in like like investing in C and making it better, um I think the returns are gonna be much higher. Um But I I I have started to reach the point where the the timescales on which like we we do good work on evolving C ⁇ . I still believe that. I still believe that the com the committee does good work.

BryceThe timescales on on which it happens trouble me. And it's it's not it's not any one individual person's fault, it's not that people are dragging their feet, um, it's just the architecture of the of the system.

Sean BaxterI think the way to deal with this is to get vendors that are active. And I I like I said before about these ideas of extension sets, like a pound pragma feature uh tuple, right? So I have that, and that has one break, which is uh comma, comma-separated expressions in parentheses now are tuples as opposed to invoking the comma operator, right? So that's a break, but you have to opt into it by using this. So I could develop this thing out, and that could become a proposal. And then it's just something you vote up or down on.

Sean BaxterAnd then if it's if it's approved, that becomes part of the next version, right? There's ways we can put out like very coarse-grained proposals. Because right now, there's too many proposals, a lot of them for tiny, and you just clog the system up. And if we had something that was big and it was like a vendor supports it and it had users, and it, you know, it's just easier to say, yeah, like we should take this thing because it's it's thought out and it's deployed and we can bang on it.

BryceSo well, and one of the fundamental problems of the C committee is that it's not 350 people working on a single project. It's 350 people, each with their own independent vision and goals, each working on their own independent proposals, with usually without a ton of consideration for what others are doing. There's there's there's there's a lack of goal setting at a high level on the committee. There's a lack of priorities, and it's not a team. It's like even if we do uh set our goals and agree that we're gonna do X, Y, or Z, or say that we agree that we're gonna do X, Y, and Z, not everybody is gets behind that.

BryceUm and without that team commitment, and yeah, it's impossible for us to work together as a committee. We we we need to have a clear vision and direction, and it needs to be something that everybody buys into. And uh and to your point about active vendors, I I'll say this this is will sound controversial, but I I fundamentally believe I'm right about this. I think it would be a much better model where the just the vendors got together and decided upon new features.

BryceUm, all of the vendors of compilers, you know who their customers are, they're users. Um and this this current setup where we have tons and tons of users and other stakeholders um uh uh involved, it it so dilutes the vendors' voices. And honestly, like it makes a lot of the vendors very, very, very um conservative um uh in what they try to do in the committee, and oftentimes it forces the vendor's hands.

BryceI I think that the people who implement C compilers um probably have a better perspective on what users as a whole need than taking a random handful of C users and saying, hey, why don't you tell the comp dictate to the compiler vendors what they should do? I'm certainly saying, like certainly user input is important, but like I just think we've gotten to this place where um there are some on the committee and in the community who think that people who develop C compilers somehow don't talk to users or like that like users are their enemies.

BryceLike that's absolutely not the case. If you're developing a C compiler, like your goal is to like serve the needs of your users. So yeah, I I in my ideal world, you know, if you look at how some of the web standards um run and some other you know more modern standards, I would I would take you know representatives from all the major vendors and I would get them together to collaborate on on new features, and I would maybe have a few people who are not from, you know, who are not compiler implementers, but it would have to be people whose full-time job is evolving the language.

Sean BaxterYeah, I'd rather have a cartel model.

BryceYeah, yeah. Yeah.

ConorI mean, doesn't um uh Python has something called, I think, the Python language summit. I maybe got the name of that wrong, but basically there are, you know, everyone can submit peps or whatever they're called, but they they also have a once-a-year language summit where only the developers that work on the Python language are are there. And like I think there's a couple people that might get special invites, but it's not it's not like a open thing. Like there's PyCon, everyone can go to that, but then the language summit is just for the language implementers.

BryceYep, I would like that model.

ConorHere's a question, Sean. So you you mentioned that one of the things that is necessary for, you know, so to summarize, you know, carbon is a vision, CPP front is a vision, all these different visions, and in your opinion, any vision uh is possible, and it's possible within the C that we currently have, and we can get to it if we want to. And you said active vendors is something that would be necessary or would help with that. Are there other things? Like it it kind of, you know, I think we had an episode a few episodes ago that was titled like uh C should leave ISO.

ConorLike, do you think these pot these visions are possible within an ISO framework, or does there have to be like a drastic governance model change in order to get there?

BryceI mean, I we know Bryce's opinion now, which is I'm not sure what your opinion is on that, but I I I well my my my my opinion is is pretty simple. Um It is likely infeasible for C ⁇ like to just for like the C standard IP to just like get up and leave ISO. Like that's I ISO I think that's another year to be more answer. Okay, like ISO has no motivation to do that.

BryceUm it'd be very complicated to do that, but um there are other ways to develop standards that get published as ISO standards. Um I'm not saying that C can't continue to be published as an ISO standard. I'm just saying it should not be developed uh uh by an ISO working group. Um I think it would be much better for uh C to form its own standards development organization to develop future revisions of C and to publish those future revisions of C through ISO's uh uh fast track processing because that would allow it to be an open standard, and it would also allow C to pick an evolution model and a stakeholder model that makes sense for C.

BryceThat to me seems like the the only practical way to dig ourselves out of this hole. Um now, if we were starting from scratch, if we could just like leave ISO completely, sure. I would say that that makes sense because in this day and age, ISO is not the right fit for C.

Sean BaxterSo that's pretty that's kind of nuanced so much. I'm still not quite exactly sure where you stand, but my case is I don't really care that much, I guess. I mean I'm just like trying to find my way through and try to arrive at a um set of language features that is expressive and kind of um continues to support existing code and provides a path for you know more productive development. And I I I don't know if the if ISO really matters that much to me.

Sean BaxterUm you know, you're gonna come out with with with standards every three years, I'm gonna do my best to implement it and keep up with the other compilers. But, you know, from my own standpoint, like um if if if there was a company that got sufficiently scared about successor languages that would be incompatible with their own source spaces, like Herb seems kind of agitated at least. Um, you know, if they want to support this, I mean they could handle the standardization approach however they want, which is ever is good for their business. Uh just like Google is doing.

Sean BaxterI mean, Google has got a different development model that works for them, or they hope will work for them.

BryceAnd yeah, it's interesting the way that you phrase that, because that helped me understand a bit about your um how you're operating. That that just what you said, that you don't really care that much about um what ISA is doing. And that's sort of the the debate that we had earlier. That your point is sort of that uh I think somebody like me, or maybe most C users, or some set of C users, presses a high value on things being standardized.

Sean BaxterNot most users, a tiny percentage. Yeah, yeah.

BryceMaybe it's tiny percent. Maybe it's tiny percent. The value of things being standardized. And your point is like, look, I'm just gonna build the best features that I can in my compiler, and other other compilers can build them if they want. Like, I want to focus on the language, not necessarily what's standard.

Sean BaxterI I wasn't up to date at all with standardization prior to starting circle. Like, I had all these ideas. I didn't know that 17 was a release year. I didn't even know that 14 was a release year, I don't think. I was on 11, and then you know, you just you do your work. Yeah. I would rarely go to the standard to look stuff up because I wasn't like writing that kind of code. I'd go to CPP reference and get you know clarification in that. Um and I I certainly wasn't reading the monthly mailings.

BryceUm and I I don't think a but they weren't they weren't monthly until the start of the pandemic.

Sean BaxterWell, okay, whatever. That's that's my point.

BryceThat's my point.

Sean BaxterLike that is like nobody cares about that. I know. And um, yeah, I mean I don't I don't have any hard feelings about the committee, really. Like, keep doing what you're doing, that's fine. If if I if if vendors like myself or bigger ones would you know periodically present you a like a mega proposal where it's a simple up or down vote, this is how you can get interface generics, like C OS concepts. And we've thought we've thought it through, we've deployed it. You can just take this thing as is, because that would make it easier to merge into the standard, hopefully.

Sean BaxterIf they want to provide that, that's like a good service. And then for customers that really just want to remain with ISO C, they would benefit from that because they would you know get accelerated features as well. Um, you know, I I just want to you know write a better compiler, a better language. And I I I think the committee has to figure out how to stay relevant.

BryceSee, I think I think most on the committee, your your your perspective is I can do valuable work on developing new C features without having to propose them for standardization. Like, like, for a lot of people on the committee, whether or not their work is valuable depends entirely upon whether it gets into the standard. They should be writing software. Right. I i like think about how the world might have been different if after you know the C OX concepts um uh debacle, um if instead of the losing side, uh uh walking away from the committee, or uh it's perhaps unfair.

BryceUm what if what if both sides had just like developed their version of concepts um in their compilers and like just not really worried that much about what the committee was doing? Like, okay, the committee didn't standardize my version of concepts, I'll just keep developing it. Um I think we might be in a better world.

Sean BaxterYeah, I think there there would have likely been a compromise at some point where they said, okay, let's and then and to be fair, that did happen for some period of time.

BryceBut um, I think eventually what happened was the folks that were working on the OX concepts and on the implementation of it, which was more mature than the concepts light, um they became disenheartened. And for them it didn't seem like it was a valuable investment of their time at some point because the committee seemed to be moving in the direction of you know this other proposal. Um and and I think that that is the the downside, I guess, that if you if if the committee does decide to do something, it's just uh drastically different than what you're doing.

BryceYeah. But but I I I do understand now, I think, a little bit better what you were uh the point you were making.

Sean BaxterYou don't need anyone's permission to write software. Just because something's right hasn't been put into an international standard document, you know, you don't need to wait for that to write software. Yeah. People aren't waiting.

BryceYeah.

Sean BaxterLike the game industry has developed their own set of tools for reflection and things, and they're like really cluey.

BryceYep.

Sean BaxterBut you know, they need it, and so they go forward and do it. They're not just waiting for the community.

BryceAnd I mean, I like even as one of the senior committee leadership, I constantly question whether the work that we are doing is valuable. Um, and I think anybody who is um deeply involved in C standardization, um you know, you stick your head up from being down in the weeds, and you have to ask yourself, was this really the best use of my time? Um was this like was spending you know six months uh uh trying to hammer out like the details of this one specific thing and this feature, was that truly truly a valuable contribution?

BryceUm yeah, and and I mean I think it's I think it's good for us to to question that. I certainly hope that lots of other people on the committee ask themselves that question. I certainly do.

Sean BaxterYeah, I'm I'm not I'm not even going there. This is all you.

BryceYeah.

ConorSo here's here's a I mean, this is kind of a specific question, but it I kind of assumed in my head when you were talking about the C OX concepts that you were in the process of adding that that was gonna be not possible to coexist with C20 concepts. But it sounds like you're still fully submissive.

Sean BaxterC20 concepts are not concepts by the they're they're what is C20 gives you? It gives you a concept definition or declaration, which is like a variable template. It's got a bool value, you give it some number of template parameters or arguments, and it's true or false. Uh and it gives you a requires clause, which you can put on the end of a template or a member, and it evaluates that, and then if it's false, then it removes it from the overload candidate set. And it also gives you like a requires expression, which is the same thing but inside an expression. These are like mechanisms that use the same keywords as C LX concepts, but they they just work as like normal language features.

Sean BaxterThey don't lock you into this alternative system of early type checking. And and the C OX concepts that I'm implementing uh or that carbon is going to implement and they call those uh interfaces and impulse and Rust calls traits and impulse and Swift calls protocols, those are basically orthogonal to what we got in 20. The early type checking does not exist in 20. It's a lot harder. Um it requires um, I think creating new kinds of data types like um generic classes.

Sean BaxterUh it's yeah, uh they'll coexist, and I think it's clear, at least in my implementation, it's clear the distinction between the C20 concept and the uh the interfaces I'm adding. There's like different set of keywords, they go in different places in the um template declarations. I'm definitely committed to to um to providing both of those. And also it's it's sort of incremental. You don't actually have to um fully opt into these interfaces because the interfaces I've written, it's like a so the interface in um in carbon or in uh uh the trait in Rust is it looks like a class specifier.

Sean BaxterSo you have an interface name, and then it's got some list of associated types, which look like type defs or function declarations for the associated functions, and that that def that defines your interface. And in my implementation, that interface is also a concept. So you can pass that around as a concept parameter, you can use that in a requires clause, you can use that to constrain a placeholder uh parameter, you can use it wherever you do uh concept, and it's just like a better C20 concept. It does type checking over the whole type as opposed to just evaluating um this Boolean expression.

Sean BaxterSo in that sense, it gives you like a half a half measure way in, and then if you want to go all the way in, you can make a generic function with the generic keyword, and that'll do the early type checking. And that's going to require like some real thought on the on the end of on the on the part of the users, because you know you have to be able to marshal all of the capabilities of the types and put those in the declaration. It's uh it's pretty challenging for me because I've never really dealt with this kind of generics before, but other languages are using it apparently with success, and people are not complaining so much about the the error messages and in these other languages.

Sean BaxterSo hopefully we get errors to be more clear and the documentation documentation would be kind of like enforced almost as part of the the definition of the function.

BryceYeah.

Sean BaxterYeah.

ConorInteresting. So this is this really is just like you're saying, you know, you said this earlier uh is just stop being scared, we can have it all, everything can live in C.

BryceLike because concepts in your concept, which is also should be the title of this up.

Sean BaxterWell, I mean, I'm I'm using new keywords to prevent uh confusion, right? Yeah. And I just like uh Carbon is using different keywords.

BryceBut but I liked how you said that the concepts that we have in C20 aren't really concepts.

Sean BaxterWell they're not, I mean, they're not the generic stuff. That's why people are still agitated. They're still angry about it. But I I think we can we can add everything. Uh I think that was one of the objections to my CPP now talk from people was that I've added a bunch of new mechanisms. You're making the language too big. They say you're making the language too big. And I and I said was that what I said was that this is reducing the time to solution.

BryceThat's that's a I I it drives me crazy when people bring up this complexity argument because I I think it's something that people bring up when they like don't like something, but they don't have any technical reason for why they don't like it.

Sean BaxterRight. Think about a um a jet cockpit. Like 50 years ago it was all pressure gauges, hundreds of pressure gauges. And that was that was a simple design. And now you have like a couple of like LCD touch panels. Yeah. And and that's hundreds of times more complicated, right? But it gives you the information you want right there. The time to solution is very quick. You can display whatever you want, it's got a whole lot more capability, yet in every way it's it's better. I mean, it's definitely more complex.

Sean BaxterDigital systems are just more complex than analog ones, but they're better at the same time. And nobody's expecting you to learn all of those things. Nobody expects you to know how every feature in in any modern device works anymore. But if you need to find it, you can find it. And and for most of your tasks, it's just much easier to use.

BryceWell, and that's there's always this specter of teachability. Um, you know, oh, well, if we add all these these things that we have to teach the old thing and the new thing. Um you know, I and people often joke about that everybody who's you know, all all the the big C figures who talk about making the language simpler, that they're really trying to make it simpler through more complexity. And people act like that's a that's like a ha ha thing.

BryceBut I think that in a lot of cases you do make the presentation of something simpler by making it more complex. And like like you do get to a simpler language by adding more features. Um I think we've we've talked about this in the past that you know at any point in time if you ask the C community how uh the evolution of C ⁇ is going, 50% of people are gonna tell you it's moving too fast, and 50% are gonna tell you it's not moving fast enough.

BryceUm Yeah, it it it's this this fear of adding new things, um the fear of adding new things solely for the the fear of adding them.

Sean BaxterRight uh I it um I think that's the one objection I don't have any sympathy for.

BryceYeah.

Sean BaxterI think I think there's a lot of like other things. Okay, I understand your opinion.

BryceBut on this one I just do not I think that's to be fair, though the the one place where uh I hesitate on this is um on on questions of like what goes into the standard library. Um yeah, yeah, yeah. Like on questions of like scope, like I'm not saying like we should add everything, like it has to still be like a valuable thing. Um I'm just saying that like there's no reason that we shouldn't add you know interfaces when we already have concepts, um, because clearly that's a thing that's valuable and that um uh would would uh you know benefit a great deal of users.

Sean BaxterWell not even saying add, I'm just saying there needs to be an active um project to discover how they would actually behave in the C environment.

BryceYeah. But I don't I don't I just I don't want to suggest that I'm saying that we should add everything that anybody might want to add to um to C in particular to the standard library. Please don't send more proposals.

Sean BaxterYeah, we're just we're just saying that uh the weight of the compiler, like the number of lines in the compiler, number of discrete features, countable discrete features, isn't a good guidance of the user experience of how complex the language is. Because you you add first class language features, the user experience improves. Absolutely.

BryceYeah. I think I think that jet that jet um cockpit example is a really good one. Um that's a really that's a really nice way of uh putting it. You know, you um if if you think about it over the past like 20 to 30 years, um computers have become far more accessible. It's like everybody's you know uh grandparents and and kids is able to use um you know a computer because they all have these much simpler interfaces, um uh and these much more user-friendly uh uh uh operating systems.

Sean BaxterAnd yet yet vastly more complex than it is.

BryceYeah, exactly. It's like like wildly more complex.

Sean BaxterAnd I think I think we can square those things. We can do that at the language design level too. I'm I'm putting in choice types, I'm putting these things in, and it's like it's it's not harder for the user. It's only harder for me.

BryceYes. Well, all right. All right, so so I think we gotta talk about the last thing that we promised the users we would talk about. Connor, have have you read Moby Dick?

ConorOh yeah. Tune in next week for part three, the final part of this three part conversation with Sean Baxter. Thanks for listening. We hope you enjoyed and have a great day.

Open the transcript file

Hosts and Guests

Guests

  • Sean Baxter Guest Inferred

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Episode 313: C++26 Reflection vs CRTP, AI, Kids & More with Zach Laine

    Nov 20, 202647 minAudio

    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:...

    • Apple Podcasts

    Credit the people on this episode

  2. Episode 312: The C++26 Contracts Fiasco

    Nov 13, 202652 minAudio

    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:...

    • Apple Podcasts

    Credit the people on this episode

  3. Episode 311: Career Changes, GPUs & More with Zach Laine

    Nov 6, 202628 minAudio

    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...

    • Apple Podcasts

    Credit the people on this episode

  4. Episode 310: Leaving NVIDIA for... ?

    Oct 30, 202624 minAudio

    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...

    • Apple Podcasts

    Credit the people on this episode

  5. Episode 309: Default Construction & CppCon 2026 with Jason Turner

    Oct 23, 202629 minAudio

    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:...

    • Apple Podcasts

    Credit the people on this episode