Menu
Sign In Pricing Add Podcast
Podcast Image

Coder Radio

592: C++ Safety Dance

Wed, 23 Oct 2024

Description

C++'s Borg-like mission continues, and some thoughts on Rails 8.1. Plus, there is a little trouble in Microsoft Paradise. And why Chris finally paid for an LLM.

Audio
Transcription

Full Episode

1.365 - 37.207 Chris

This is Coder Radio, episode 592, recorded on October 22nd, 2024. Hey friend, welcome in to Jupyter Broadcasting's weekly talk show. It takes a pragmatic look at the art, the business, the software development, and the world of technology. My name is Chris, and keeping an eye... On the world, it's our host, Mr. Dominic. Hello, Mike. Hello, Chris. Yeah. I've decided you are our C++ correspondent.

0

37.407 - 54.497 Chris

What a mixed honor. You know, like, if we were to bring you on to another show, we would be like, host of Coderator Program and Jupiter Broadcasting's C++ correspondent joins us tonight to break down C++'s continued Borg-like mission. Mr. Dominic, what are you learning...

0

56.007 - 62.982 Dominic

Well, you know, that feature you just got there, Go and Rust, C++ has already assimilated it, and your science will service them.

0

63.643 - 64.926 Chris

We would like some of that, please.

0

67.202 - 69.744 Dominic

They just wait. They're like, what are they doing?

69.764 - 92.26 Chris

Do you think, so the safe C++ extension proposal, which was last month, like late last month, which is an evolution in C++, a proposal for safe C++ extensions to enhance memory safety and, you know, basically respond to the great threat that is Rust. Exactly, right.

92.56 - 95.542 Dominic

Rust in the Linux kernel? Okay, we need to do something here.

96.563 - 117.794 Chris

So the work's being done via the C++ Alliance. Its president and executive director, Vinny Flacco, said that it was, quote, a revolutionary proposal that adds memory safety features to the C++ programming language. You know, this kind of – the article that we'll have linked to the show notes kind of puts it in context. And it is worth mentioning, right?

117.974 - 139.513 Chris

So in 2020, Google did a little study and identified that 70 percent of Chrome's severe vulnerabilities were memory safety issues. We've also – we also saw another study came out that the White House cited in February. And their national cyber director. We actually talked about on the show really briefly where they kind of came out.

Comments

There are no comments yet.

Please log in to write the first comment.