CppCast - Podcast News and Updates

Episode Date: May 12, 2022

Rob and Jason discuss various news articles, libraries and announcements. News Lexy First Beta Release I made an Online C++ Compiler GCC 12.1 Release Join your local user's group

Episode 349 of CppCast, recorded May 9th, 2022. In this episode, we discuss an update to Lexi, an online compiler tool. And we share some of our own news. Welcome to episode 349 of CppCast, the first podcast for C++ developers by C++ developers. I'm your host, Rob Irving, joined by my co-host, Jason Turner. Jason, how are you doing today? I'm your host, Rob Irving, joined by my co-host, Jason Turner. Jason, how are you doing today? I'm all right, Rob. How are you doing? I am doing okay.

Don't think I have any news to share, or we'll have a lot of news to share in a minute, I guess. But we'll get there. How about you? No, nothing particular. I don't think I've mentioned that I did actually have a TOX accepted for C++ North. Oh, nice. Yeah, I got the acceptance like a month ago, but it leads to a complicated trip for me because I have to fly back from England to Canada on my way home to do this.

Well, it'll be a wonderful time to be in Canada, though. Yeah. Did you get accepted right after we had Stephanie and Diana on? Yeah, I think it was like the next week or something they sent out the initial acceptance emails. Very cool. All right. Well, at the top of every episode, I'd like to share a piece of feedback. We got this tweet after last week's episode with Joel de Guzman. And this is another recent guest, Rene Fernan Rivera-Morel saying, Hey, Joel, nice episode. This rounds out CppCast interviewing everyone who once upon a time worked for BoostPro. Eric, actually,

Eric Niebler commented, was I on and don't remember? Eric definitely was on. Yeah, Eric on. Yes, I think it was within our first year of doing CPVcast and we talked about ranges with him. I looked up the episode, but I can't recall what it was now. Sorry. It was definitely in the first year or two. Yeah, I think it was in the first

below 150, definitely. It was in the first couple of years. Then it had to be below 100 if it was in the first two years. I think we may have mentioned Boost Pro, the consulting company. I mean, I guess we have had all the former engineers from there on. Did we mention that with Joel? I don't know. I don't recall actually mentioning the company.

Are they still around? Like, still doing work? I don't think so. Okay. It's an interesting era. Well, for someone who's old like me, this came up in our last interview, right? Where the discussion of like, well, can you make money as an open source company?

And there was a timeframe in the like late 90s that you had like Red Hat and stuff going public. And their stocks, I mean, it was perfect timing for the dot-com era. They got swept up in the dot-com era. Their stocks skyrocketed. My understanding is that actually Linus made a fair bit of money because all those Linux companies, as they went public, they gave him a few shares just as a goodwill token,

like, thanks for creating Linux. And if he managed that wisely, then it would have been a lot of money today. It'd probably be worth almost nothing, because I don't know how many of those companies even still exist. But yeah, interesting. All right. Well, we'd love to hear your thoughts about the show. You can always reach out to us on Facebook, Twitter, or email us at feedback at cpcast.com. And don't forget to leave us a review on iTunes or subscribe on YouTube. And it's just us today. Just us. I guess we'll do some news first and then talk about our own news. Does that make sense to you, Jason? I think we may as well. We've always

had news. Always had news. Okay. So what do we have? First up from Jonathan Mueller, an update to Lexi, a C++ parsing DSL library. And this is the first beta release. And I know we've talked about Lexi before, probably over a year ago. But I guess it's had plenty of new features. And I guess I'm not sure if he's calling this a 1.0 or if it's just maybe more stable going from alpha to beta. I got the impression from Twitter, I guess. Maybe I'm missing something here. That this was, it's the first official release.

Everything else has just been, you know, go and check out the GitHub repository. This is the first like tagged release of Lexi. But it's a parser generator, basically. Yeah, parser generator for DSLs. I have not really looked too deep into it. Have you? When it was first announced, I looked a little bit closer. I haven't looked recently in depth into it.

I did see one thing he highlighted in the Reddit post is arse tree generation. And there's this playground website with a compiler explorer like interface where you can have some code using Lexi and see the output of it, which seems pretty nice. That is fancy. Very fancy. And this is perfect. I said a few weeks ago that I put out a challenge to anyone who wanted to start a YouTube channel that they could do a response channel.

I don't know if you saw this, but someone did do a response video to one of ours. They covered some of the news items, and it's actually, I believe, people who go to my meetup, people who are local to Colorado. So this is definitely something, like if you're out there thinking, I want to really get into YouTube, this is definitely something that you could cover in your YouTube videos.

Next thing, speaking of that Compiler Explorer-like feature that Lexi has, this is another post on Reddit with someone making their own online C++ compiler. Yeah, link is here in the show notes. This one also kind of looks similar to compiler explorer. And I think people were asking in the comments, what differentiates this between your site and compiler explorer? And I think this is more mobile optimized. Yeah, a little bit more.

What's the word? Responsive layout? Yeah. When I first clicked on this, it was broken. But just now I checked, and it did work. It did run the program. It doesn't give you the disassembly. It's not that kind of focus.

It's more like, what's the other online compiler? Is it the wand? Q-Karulu? Another OneBox or something? Yeah, yeah, yeah, okay. Yeah, more like that. Right, so if you want to test out some C++ code and you only have your phone or tablet available,

this is a good option for you. Got a good URL, too, goonlinetools.com. Oh, I didn't notice that. That's pretty good. Wait, are there other goonlinetools? That's a great question. I didn't notice that. That's pretty good. Wait, are there other GoOnline tools? That's a great question. I didn't go up to the top domain. There is. Random number generators.

Random string generators. Random emoji generator. Interesting. What? Instagram caption generator. They have a lot of tools here. Okay. DSS formatter. Interesting.

Okay. And they have other compilers too. They have Python. They have Java. PHP. Okay. Online photo editors. What in the world? Well, I'll have to keep this site in mind. It looks like they have

a bunch of interesting tools. Lua Beautifier. XML to JSON. And CSV to XML. Interesting. That's, well, then you could do CSV to JSON. Wait, how would that work? Wait, how would CSV to XML work?

Because you would need object. JSON to XML makes sense to me. I don't know about the CSV to XML. What is that? It's JSON to XML. XML to JSON sounds harder to get right. Like you would need a set of heuristics to guess what object name should be and stuff. Or make it overly

generic in a way that would be difficult to work with. Yeah. Interesting. Markdown, I don't know. What in the world? Okay. Spend the whole show walking through all these tools. You really could. Good stuff. You've got an online screen recorder in here.

What? I asked that. Anyway. QR code generator. Everyone needs a QR code generator. That's pretty cool. I have to see this. Hey, it works.

Where's my cell phone? I take a picture real quick. And then the next thing we have is GCC 12.1 is being released. This is a major release, 35th anniversary. I think we talked about some of the features that were being put out in this a major release, 35th anniversary. I think we talked about some of the features that were being put out in this release last week, right? Yeah, we did cover it, but it's now official as of May

6th, I guess. So three days ago from the time of recording this episode. So definitely a good time to go update your compilers, get the latest goodness. One random thing in here that on the security side, GCC can now initialize stack variables implicitly using the f trivial auto var init to help tracking down and mitigating

uninitialized stack variable flaws i'm just concerned that it would just makes cross-platform code more difficult in a way because i prefer the idea of like what visual studio does we're in a debug build all memory is default initialized with recognizable patterns cd cd cd by default right right and then if you have uninitialized value and you jump bump into the debugger and you see that cd cd you know why in this case you might just end up relying on default initialization to zero and not know what happened i mean you could argue it's a flaw in the language but we can't fix that because that would break all kinds of backward compatible well would it break if we now specified in the language that stack variables were default initialized, would that break existing code?

It would only break existing code that relied on undefined behavior. Right, yeah. But you would definitely get people crying that it just pessimized their code because now there's a zero right in there that they didn't want there to be before, and there's an extra three bytes in the binary and an extra instruction added. Interesting. Alright, the last thing we have here isn't necessarily new news, but I think this is a post that Jens Weller on Meeting C++ makes every month with upcoming C++ meetups.

So any meetup that Meeting C++ is aware of, all the meetups for that month will be posted here. As you can see, there's Denver, your monthly meetup, Jason. We're actually meeting back in person for the first time in just over two years. That's exciting. Yeah, it's kind of crazy. Wow. If you want to find out if there is a C++ meetup in your area, definitely go check this site. Yeah. Probably the best way to go find one. And if you run a meetup and it's not currently on the meeting C++ website, there's a link somewhere on here to submit your...

Get yourself listed. Yeah, get yourself listed. And Jens does a good job of getting these all updated. There's a lot in Germany, I will say that. And a couple in Poland. Yeah, a lot of European ones. Yep, yep. Vienna. Maybe I should go to the Vienna meetup on the 19th. No, that's not going to happen. Actually, I don't even know if that's in person. Most of them are still online, just for the record, but things are slowly changing. That one is in person. The Vienna one at the end of the month is in person.

Okay. All right. Well, I guess there's no other time but now to talk about our news for this episode. And if you saw the episode title, it'll probably have given away. We're going to have to figure out what the episode title is going to be. I mean, maybe we want to trick people. Maybe we want them to think it's a normal episode right up until now. Maybe. Or, I don't know, several of my favorite YouTube channels have had big news episodes and they come down to like, oh yeah, I'm currently moving.

And so I won't have any episodes for the next week. And then you're like, wait, is that kind of clickbait? I'm not opposed to doing a clickbait title. We could give it a shot. We could just say Big Channel News. We could. We could. Well, so people aren't hanging on for any longer wondering what we're talking about. We are going to be, I guess, going on an indefinite hiatus is what we're calling it. Yeah, indefinite hiatus.

I think that's what we settled on, yeah. Yeah. Yeah, I guess I'll start because, you know, it was me who really initiated this plan to go on indefinite hiatus. But yeah, like a few weeks ago, I kind of was just publishing an episode and was wondering to myself, you know, why still put this much effort into the podcast each week. And that sounds really mean in a way and very selfish maybe, but... Not at all. We've been doing it for seven years, and I kind of got a lot out of it, obviously. I think we both have. But I'm not sure if it makes sense to be doing for me anymore.

I recently changed jobs. And I think I mentioned this like two months ago. And I have in the past thought about looking for a job in like developer evangelism. And after this recent job change, which is not evangelism at all, I kind of realized that that's probably not going to happen. I'm very, very happy with my new job. But because I doubt I'm going to be going into developer evangelism, I kind of just thought, you know, maybe it doesn't make sense to be doing the podcast anymore because it doesn't, you know, directly impact my career in any way. I should say the new job has been mostly.NET. Yeah, I was going to say, you should point out that you're not actually doing C++.

I am not doing C++. Although, you know, when we talked about this, I've been talking about it a lot over the past few weeks. But, you know, I told you how within the first month, month and a half, I've only been doing.NET. I actually touched C++ at my day job yesterday or Friday and today. Perfect timing. Perfect timing. Just a little bit. I'm doing a lot of web development in.NET with Blazor WebAssembly. Listeners have heard of that. It's.NET's version of doing WebAssembly website development. And I needed to get a native library into my Blazor project. So I spent some time with Inscripten. Nothing too complex, but I did get a little bit of C++ in the last few days.

That's cool. Yeah. But yeah, anyway, just to go back to what I was saying, I just kind of felt that I have been mostly doing the podcast recently like for the community and not as much for myself that kind of made me think maybe it is a good time to step down and move on yeah how about you do you want to talk about why you decided to follow me while ending the podcast. What was it? Indefinite hiatus. It's possible that we or someone else perhaps might pick up this mantle at some point.

We don't know. It was nearly about three years ago that I tried to abdicate some of my responsibilities when I was traveling all of the time. And I suggested that we find like an ad hoc, you know, someone to come in and be an occasional co-host because I was traveling a lot. And I have gotten so much out of the podcast from things that I learn, meeting people, exposure for my training business and all that stuff. But that didn't really pan out. Turned out that it was hard to

find people who wanted to co-host. We've had a few episodes where you were away doing training or a conference and we needed to have a co-host. And, you know, I found a few for that purpose. But yeah, it was kind of always a little difficult to find someone who was up for kind of doing an episode. Yeah. Yeah. And, well, I mean, like you said, we've been doing this for seven years. How many? Oh, yeah, right. I was thinking how many episodes and whatever,

or guests, but we'll talk about that later, right? Seven years is a long time. And I've never kept a job for more than four years. Arguably, this is the longest job I've ever had. Although it's also the worst paying job I've never kept a job for more than four years. Arguably, this is the longest job I've ever had. Although it's also the worst paying job I've ever had. That's very true. It's almost the longest job for me too, because my first job out of college,

I'd stay there for like eight years. I started the podcast just a few months before leaving that job. And then I did my previous job for like six and a half, almost seven years. And then now just started this new one. And yeah, the podcast has been my second longest job. Yeah. And with an hourly rate comparable to your first job. Yeah. I mean, we weren't doing it for the money, obviously, but it's been a lot of effort in a long time. And it's just time feels like it's time to move on to something else. Yeah, it has been, I should say, you know, just kind of going back to my reasons, you know, obviously, I've always enjoyed doing every single interview, you know, talking with you each week talking to the

guests. But there is, you know, a fair amount of work that goes in besides that one hour interview. You know, we prepare show notes, we have to go find new guests, we do editing, we might do publishing. So, you know, that time does take away from, you know, free time that I would be spending with my family. I have to put in a little extra work if I'm recording an interview during my normal work hours. So yeah, that takes an hour and a half out of your work day every exactly an hour and a half out of your work week every week, basically, at least. And then I don't know how long you spend like preparing the stuff. Just for the record, everyone, Rob has always been the one who did all

of the hard work here. I would help with show notes and the interview and everything, but I still estimate it probably took about three hours a week for me. So I have to assume it was at least five, six, seven hours a week for you, which is notable. Yeah, maybe four or five. It would be my guess, but I'm not keeping a running tally. Yeah, no, but yeah, I mean, and like I was saying, I've been really thankful that current job and previous job are very flexible with having no problem with me doing a podcast interview in the middle of my 9 to 5 work day.

But it does take away and I have to make up that time later because the podcast is not my full-time job. Maybe if it was, I'd keep it going forever, but it's not. Yeah. That note of keeping it going forever, I'm going to jump ahead a little bit from our plan here because you saw this tweet recently from Angie McEwen. Yeah, I think this tweet just kind of was going a little viral

one day a few weeks ago, pretty much right after I started talking to you about going on this indefinite hiatus. And I'm just going to go ahead and read it because it definitely spoke a lot to me. So here's the tweet. I think this was like copy pasted from Reddit or something else or Tumblr, maybe. I think a lot about how we as a culture have turned forever into the only acceptable definition of success. Like if you

open a coffee shop and run it for a while and it makes you happy, but then stuff gets too expensive and stressful and you want to do something else. So you close it. It's a failed business. If you write a book or two, then decide that you don't actually want to keep doing that. You're a failed writer. If you marry someone and that marriage is good for a while and then stops working and you get divorced, it's a failed marriage. The only acceptable win condition is you keep doing that thing forever. A friendship that lasts for a few years, but then its time is done and you move on is considered less valuable or not a real friendship. A hobby that you do for a while and then are done with is a phase or alternatively a pity that you don't do that thing anymore. A fandom is dying because people have had a lot of fun with it but are now moving on to other things. I just think that something can be good and also end

things still good. And it's okay to be sad that it ended too, but the idea that anything that ends automatically less than this hypothetical eternal state of success, I don't think that's doing us any good at all. And yeah, I read that and it definitely spoke to me. And I don't think CppCast is a failed podcast. Even if we never do another episode, we had over 300 successful episodes. We're like Seinfeld, right? So Seinfeld said, we don't want to fade out and die slowly as a TV show. They intentionally ended while they were still at the top of the ratings. Now they ended with one of the worst series finales

that's ever been put on TV. Not a good episode, yeah. No, but that's ever been put on TV. It's not a good episode, yeah. No. But that's not the point. The point is they still went out while they were on top. We're still the most listened to C++ podcast, so we're going out while we're still number one. As far as we know.

I mean, we don't see anyone else's numbers, but ADSP is doing real good. I mean, hopefully they are. Yeah, hopefully they are, yes. Yeah. We should have had a list of other podcasts in here, but we didn't put that together. I mean, we can put that in.

I mean, ADSP is great. I've listened to a bunch of their episodes recently. What is that? The acronym actually stands for Algorithms Plus Data Structures Equals Programming. I think that's right. Yeah. And then Twoos complement. Twos complement.

Is the other one TB hit is one? Yes. Yeah, yeah, yeah. That's JF's, right? That's JF Bastion. That one is not very regular. I saw someone commenting that they just released a new episode and it was like exactly a year since the previous one.

But I'm sure it's good content. Yeah, an ADSP is quite regular. None of the ones that we just mentioned are C++ specific. There's also CppChat, but I think they've taken a little bit of a break as well. I don't think they put out an episode recently. But they were always a little bit more regular.

I guess the next thing we should say is that we want to thank and say how much we appreciate everyone who's supported and listened to the show over the past seven years. So thank you to all of our listeners. Thank you to all of the patrons on Patreon who've been supporting the show. Did want to mention that although we'll be shutting down the CPP cast, Patreon, Jason, you still have your own Patreon for C++ Weekly, right? I do, yeah. I'll talk a little bit more about that in a little bit. But yeah, so if anyone is interested,

because I know a couple of people told me that they stopped supporting C++ Weekly's Patreon and moved to CBPCast to spread the love around. Well, CBPCast's Patreon is shutting down. You're welcome to move back. That's all I'll say. And then also want to definitely thank all of our sponsors who supported the show over the years. We've pretty consistently had sponsors

almost forever at this point, right? Yeah, I mean, we very early on got sponsorship We've pretty consistently had sponsors almost forever at this point, right? Yeah. I mean, we very early on got sponsorship. ThinkShop Brains was the first one. That sounds... Yes, right. Because we both recorded ad spots for that. I remember doing that.

And it was a little awkward for me because at the time I didn't use IDs at all. And I'm trying to record an ad spot for Sea Lion. You later on did start using Sea Lion. Yes. That's funny. And then obviously, other people we really want to thank. All of the guests we've had on the show, although

we've done a handful of episodes that were just the two of us talking about news and such. What, like 10 or something maybe? About that, probably. The guest would not have been successful if we weren't an interview show, you know? No.

So thank you to all of the guests who came on to talk about your books, your libraries, your conference talks, everything. And you added this up, 294 unique guests. Yes, 294 guests we've had on the show. Obviously, we've had several guests on, you know, sometimes twice, sometimes, you know, four or five times. But yeah, 294 unique guests have been on CPP cast. That does include you. It does me. I was episode number two. I feel like I should take this opportunity to apologize too, because I mean, 294 guests, right? So like at CBP con last year, well, maybe not last year,

but at CBP con, I've definitely had people come up to me and say like, Oh, you know, hi. Like, and I'm like, and I look at them and I'm like, no, I should know who you are. And then I pull out my phone real quick and I'm like, oh shoot, they were a guest on CDP cast. I interviewed this person, but that's a lot of people. It's really hard to keep all that straight. Yeah. I have not had that problem. I guess I also don't go to as many conferences as you, but I typically am really good at remembering faces, but just not remembering someone's name. So I'll see the person and know that we talked to them, but it takes me a moment to realize who they are and what we talked about. Oh, well, shoot. Yeah. And even if I immediately remember,

oh yeah, I've had you on the podcast, remembering what we talked about. I need the 10-second memory jog to reshuffle the LRU hash up to the top here. Yeah. What else do we want to talk about, Jason? We did want to put in these plugs for all the upcoming conferences. I'm not sure if I'll be making it to many of these in the near future, because like I said, I'm not doing much C++ development right now, but I think you'll probably be a lot of these, right?

I don't know, actually, because I just, well, it's interesting. So I'm keynoting at C++ on C. That's the next C++ conference coming up that I know about. That's July 5th through the 7th. Workshops are on July 4th. I am offering a workshop on doing code reviews. So that's in Folkestone. You still have time to buy a ticket

and buy airplane tickets to England. Travel is really surprisingly easy at the moment. The next conference coming up in DC Tech Town, that's the one that's in... Is it Oslo? No. No? It's not in Oslo. It's in the town that's good. I can't remember what town it's in.

Shoot, I've been there. One of us, see who gets to it faster. Kongsberg? Yes. Yeah, yeah, yeah. Kongsberg. Okay. So that one is August 28th through the 31st.

I'm not currently planning to do that one, but I just want to make sure we mention all of the, because we'd like to talk about conference news, right? This is going to be our last episode. Let's make sure that at least everyone knows about all the conferences that have been announced right now. Oh, I'm guessing C++ Now probably just announced their dates for 2023, but I did not think to grab that.

That'd be in May. Let's see if I can check right now. So Core C++, that's the one that's in Tel Aviv. September 5th through the 7th is coming up. CVPCon, September 11th through the 16th is coming up back here in Aurora, Colorado. And Meeting C++ has officially announced that they are a hybrid conference November 17th through the 19th. I'm not seeing any dates for C++ now next year. Okay.

They usually announce the future dates on the last day of the conference. So if you're feeling particularly ambitious, you could be in Folkestone August 28th through the 31st, then fly to Israel, not Folkestone, excuse me. You could be in Kongsberg and you could be in Norway the 28th through the 31st, then fly to Israel for the 5th through the 7th, and then fly back to Aurora for the 11th through the 16th for CBPCon. Now, I just actually noticed yesterday, I was looking at my calendar and realized I actually

have a very important family obligation that partially overlaps with CBPCon. So even though it's in my backyard, I don't even actually know if I'm going to make it to CBPCon. Interestingly. I was a little bit of a surprise when I realized that. It's my grandma's 90th birthday so I kind of have to go to that. That's very important. I can't miss that. Where's your grandma? Is that in Denver? It's going to be in Florida. It's not like I can drive to the conference and then drive to the party or anything like that. No, that would not work out.

No. So that was kind of a little surprising, kind of funny in a way when I noticed that. Yeah. So the only one that I know for sure I'm going to is C++ on C, but we'll see about the others that I don't have other obligation to collapse with.

I guess we didn't have CPP North on this one, but we just had them on and that one is in July, right? Oh goodness. How did I miss that? Yeah. I'm sorry. Let's make sure we add it to the notes. Yeah. CPP North. Right. And that one I am planning to speak out right now i was accepted and i just have to

figure out this relatively complicated trip of getting back from europe to canada to make it home right okay and then you want to talk about some other stuff that you're going to be up to because although you know i might not be as active in the C++ community, you still will be without CppCast. I am not dropping out of the C++ community. It's not like I'm dropping out. I'm just not going to be as active. Right, right, right, right. So let's see.

We've got... I want to say, if you want to book training, this is my last chance to advertise the fact that I do training on CBPCast. I am still doing training. A lot of companies are returning to the office. You should hire me to come to your office to do training. I just updated my website. We'll have a link to it because I wanted to be more explicit about my style.

And I'll take just the two-minute elevator pitch here. First of all, every company needs C++ best practices training. It is not the only thing that I do, but you all need best practices training. Trust me, because I've seen enough to know that you all need it. But just in general, the way my training works is I've got a bunch of curricula on my website, suggested possibilities for classes.

You contact me and you say, we want this curriculum. And I say, that sounds great. We settle on a date and a length of class that you want. And then shortly before the actual class, like say one to two weeks before the class, I will send the students a pre-class survey. I use that survey and the information that I glean from that to customize the class specifically to those students. As far as I know, I'm the only one that customizes my classes this much to the students. Then I further customize the class

throughout the length of, you know, I recommend two to three days, but anything from one to five is possible depending on where you are and whatever. Even throughout the class, each evening, go back to the hotel. I'll customize what we're going to talk about the next day based on the kinds of questions that the students asked or whatever. And I'm continuing to do code reviews. I've gotten a surprising number of people asking for code reviews lately. So I also put some information up on that link that we'll be listing. And that can be, again, fully customized.

Do you want me to give you a formal report back or do you want like an ad hoc YouTube stream kind of code review? Like many, I mean, I've had thousands of people watch those code reviews. So far, I've published three puzzle books. I don't think I knew about the third one. Yeah, we talked about the third one, I think, right?

Yeah, the third one I didn't do a good job of advertising. It's Opcode Puzzlers, and it's basically like a limited instruction set machine and only 8-bit operations, and you have to actually execute all the operations and decode what the message was that was created in memory. I have four more in the works, so I know I'm going to publish at least a total of seven. My goal, which I never told anyone publicly, but now I'll go ahead and spill the beans, was to do 10 puzzle books in the course of 2022. So I know I'll get seven out the door.

Oh, yeah. C++ Weekly does not plan to stop anytime soon. I plan, I think my last plan was to cover the release of C++32 and then I'll retire. Really plan that far ahead? Well, I mean, if you just look at it

like that'll be like nine more years or whatever, ten more years of doing C++ Weekly. I'll be in my 50s. I'll probably be tired of releasing an episode every single week, but no telling. And you're also planning on bringing your other YouTube channel back up to speed, right?

Yeah, so my other YouTube channel, The Retro Programmer, which kind of has an interesting history in my head that I don't give it enough credit for. You mentioned it when you introduced me at CVPCon when I gave the rich code for tiny computers, the Commodore 64 talk that everyone liked. Because it was on that channel that I first demonstrated that it would be possible to run modern C++ code on a Commodore 64.

And then that was actually seen by Herb Sutter, who then invited me to give the talk at CVPCon. And it's on my to-do list to thank Herb still for that opportunity again, thank him again for that opportunity, because that had a significant impact in the rest of the things that happened over the last five years. That was a lot of visibility in that talk. Do you have videos playing that you're going to be doing on that channel?

Yeah, so I'm going to toss it up a little bit. Right now it's called The Retro Programmer. And C++ Weekly, I mean, I kind of have to release an episode about c++ every week with that channel in case it wasn't obvious and my viewers punish me if i do something that's not like a new c++ feature or some sort of gotcha i get like a half to a third as many views. So you can't like do a Rust episode there. I could. A Rust episode, that's cheating

because that would be clickbait at that point. But I can't do any other random topic that interests me, basically. So I'm going to rebrand the retro programmer. I'm currently planning to call it literally the fill in the blankthe-blank programmer. So then each episode, I could be like the object-oriented programmer and cover some design patterns. Or I could be, I have a bunch of ideas, the SQL programmer.

And just have an episode on what is a relational database. Things that I've worked with in my career. My career's been a lot longer than just C++ focused, but I never talk about any of the other things that I have experience with. And I just feel like it'd be another creative outlet, I guess.

And with that, I'll have a few extra hours a week to put together those episodes. Okay. Well, I should also say, Jason, if I haven't said it already, that one of the things I am going to miss the most is just having a chance to catch up with you and talk about stuff every week. We'll definitely still keep in touch, but we'll be missing that. Yeah. Thank you, Rob. And it's been, like I said at the start of this, the opportunities that were opened up here and the opportunities that you gave 294 people by creating CBPcast, honestly. We don't talk about

this so much publicly, right? But we might have like a book author come on and they'll talk about their book and then they'll tell us like three months later that they're still seeing a tail in increased book sales from being on the podcast. There's been lots of people who were just starting out in the community and you found them somehow and they've gone on to do very significant things and lots of conference talks and important open source libraries and whatever.

So I think it's been significant experience for a lot of people. Yeah, I've definitely, like I said before, I've enjoyed every single episode that we've made. I'm really proud of what we've done with CppCast. And it's definitely, you know, having a lot of bittersweet feelings, like, are we actually letting this go right now? But like we said, we kind of both feel like it's a good time to step down. Who knows?

Maybe a month from now, we'll find ourselves really missing this and change our minds. Maybe a year from now. Who knows? We'll see. Ready to take a break for now. Yeah. Ready to take a break for now. Yeah, ready to take a break for now. And I also want to say that I'm proud of us, I guess, for consistent. We didn't miss a single episode for the two years that a lot of people pretty much weren't leaving their houses because of COVID. And we got feedback from a bunch of people about having that consistency specifically in the first year

was very important to them. Glad that we did that. Yeah. Up until the first year of COVID, we usually kind of maybe missed a week or two per year, but we did have a good long-running consistency for the first year and a half or two years of COVID. I don't know if there's anything else to say at this point.

Again, thank you to everyone for listening. Thank you for everyone who's been on the show, everyone who supported the show. We'll still be around, especially you, Jason. I'm not really going anywhere. You just can't email me and ask to be a guest on the podcast anymore. And I guess we should probably take just a moment to apologize because there's a couple of people left who we had kind of said, oh, well, maybe we'll have you on the podcast soon.

And we haven't told them that we were canceling the podcast. I got at least three or four emails over the past few weeks after we had decided we were going to do, you know, end on this episode because we had booked two interviews and then said we'll end after that one. And yeah, I apologize to those potential guests who have not responded to. And just thank everyone for listening. Again, maybe we'll be back someday, but taking a break for now. Yeah. Thanks, Rob.

Thank you, Jason. Bye, everybody. Bye.