Loading video...

Video Failed to Load

Go Home

Brian Kernighan: Rust is "a pain" The C and UNIX legend says the Rust programming language is "incomprehensibly big and slow", "I don't think it's gonna replace C". Bonus: What Kernighan thinks of NixOS.

LundukeJournal's profile picture

The Lunduke Journal

26,147 subscribers

10,945 views • 1 year ago •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

I thought Rust was supposed to replace C and C++, not Java and Scala. But xAI's new x-algorithm repo tells a different story... and Rust is only a part of it.
7:44

I thought Rust was supposed to replace C and C++, not Java and Scala. But xAI's new x-algorithm repo tells a different story... and Rust is only a part of it.

Forrest Knight

175,171 views • 8 months ago

Is Rust the least secure programming language? There was yet *another* massive Rust security failure... and nobody seemed surprised. Most Rust activists simply shrugged at the normalcy of it. Considering the frequency and severity of malicious code being added to the Rust Crates ecosystem... is it the least secure programming language toolchain?
8:11

Is Rust the least secure programming language? There was yet *another* massive Rust security failure... and nobody seemed surprised. Most Rust activists simply shrugged at the normalcy of it. Considering the frequency and severity of malicious code being added to the Rust Crates ecosystem... is it the least secure programming language toolchain?

The Lunduke Journal

18,230 views • 1 month ago

I implemented a small subset of the Ken Thompson's B Programming Language in Rust and used Raylib from it.
0:58

I implemented a small subset of the Ken Thompson's B Programming Language in Rust and used Raylib from it.

Тsфdiиg

31,418 views • 1 year ago

Simon Peyton Jones is the co-creator of Haskell (pure functional programming language) and I interviewed him about functional programming, why it matters, and his thoughts on other programming languages. In this episode: • Useful and useless programming languages • Rust vs C • Haskell vs OCaml • Why functional programming matters • Static languages and their value for LLMs • Why Excel is his 2nd favorite programming language Where to watch: • YouTube - • Spotify - • Apple Podcasts - • Transcript - Thank you to the sponsor of this episode for supporting my work: • WorkOS: makes your app Enterprise Ready with easy to use APIs to add SSO, SCIM, RBAC, and more in just a few lines of code, check them out at Chapters: 00:00 - Intro 00:39 - What functional programming is 09:18 - Downsides of functional programming 10:53 - Specialized hardware for functional programming 21:47 - Haskell is useless 25:59 - Rust vs C 28:26 - Haskell vs OCaml 35:26 - Side effects in Haskell 44:26 - Type systems 57:30 - How the Haskell compiler works 01:04:35 - Why Haskell is talked about more than used 01:09:07 - Avoiding success at all costs 01:11:12 - LLMs and programming languages 01:13:57 - New programming language design 01:15:59 - Should students continue to learn programming 01:22:33 - Why Excel is is 2nd favorite programming language 01:25:04 - Advice for his younger self
1:27:52

Simon Peyton Jones is the co-creator of Haskell (pure functional programming language) and I interviewed him about functional programming, why it matters, and his thoughts on other programming languages. In this episode: • Useful and useless programming languages • Rust vs C • Haskell vs OCaml • Why functional programming matters • Static languages and their value for LLMs • Why Excel is his 2nd favorite programming language Where to watch: • YouTube - • Spotify - • Apple Podcasts - • Transcript - Thank you to the sponsor of this episode for supporting my work: • WorkOS: makes your app Enterprise Ready with easy to use APIs to add SSO, SCIM, RBAC, and more in just a few lines of code, check them out at Chapters: 00:00 - Intro 00:39 - What functional programming is 09:18 - Downsides of functional programming 10:53 - Specialized hardware for functional programming 21:47 - Haskell is useless 25:59 - Rust vs C 28:26 - Haskell vs OCaml 35:26 - Side effects in Haskell 44:26 - Type systems 57:30 - How the Haskell compiler works 01:04:35 - Why Haskell is talked about more than used 01:09:07 - Avoiding success at all costs 01:11:12 - LLMs and programming languages 01:13:57 - New programming language design 01:15:59 - Should students continue to learn programming 01:22:33 - Why Excel is is 2nd favorite programming language 01:25:04 - Advice for his younger self

Ryan Peterman

128,845 views • 4 months ago

This is gonna make Rust programmers angry. Reflection is one of the most powerful concepts in Computer Science. Unfortunately, not every programming language is blessed enough to have it. Timestamps: 00:00 Powerful Computers have No Security 03:07 Reverse Engineering is Program Surgery 04:55 The first .COM in History 06:56 The Least Private OS Ever Created 09:33 Rebooting, Never? 12:41 Reflection Tier List Ranking 16:13 C++ is getting COOL 18:22 Rust is…Rough 20:13 God-Tier Reflection 22:27 Blessing C++ with…Metadata? 26:44 Rebelling against the Machine
30:15

This is gonna make Rust programmers angry. Reflection is one of the most powerful concepts in Computer Science. Unfortunately, not every programming language is blessed enough to have it. Timestamps: 00:00 Powerful Computers have No Security 03:07 Reverse Engineering is Program Surgery 04:55 The first .COM in History 06:56 The Least Private OS Ever Created 09:33 Rebooting, Never? 12:41 Reflection Tier List Ranking 16:13 C++ is getting COOL 18:22 Rust is…Rough 20:13 God-Tier Reflection 22:27 Blessing C++ with…Metadata? 26:44 Rebelling against the Machine

LaurieWired

192,174 views • 2 months ago

People in rust use sub human all the time, crazy enough this dude here also calls jewer subhuman. I dont think this dude even knows hes talking to jewer. And i think the reason why winnie is even saying that is because of this clip. Winnie has a so many hours in rust i REALLY DOUBT he knows a small detail of nazi language. be fucking honest here lmao
0:55

People in rust use sub human all the time, crazy enough this dude here also calls jewer subhuman. I dont think this dude even knows hes talking to jewer. And i think the reason why winnie is even saying that is because of this clip. Winnie has a so many hours in rust i REALLY DOUBT he knows a small detail of nazi language. be fucking honest here lmao

Throat

82,482 views • 2 years ago

“I didn’t want to be rude and leave anyone out, A lot of us don’t play rust a lot and we’ll lose to these big guys like camsoda” The burnt peanut says the big rust streamers can play but can only use primitive weapons 🤣
0:30

“I didn’t want to be rude and leave anyone out, A lot of us don’t play rust a lot and we’ll lose to these big guys like camsoda” The burnt peanut says the big rust streamers can play but can only use primitive weapons 🤣

The Burnt Peanut Clipped

339,263 views • 6 months ago

👀Decisions are being made today. If restarting the #XRP ledger from scratch, Ripple CTO David Schwartz discusses using "Rust" is definitely talked about. Proposals from an outside company are currently being considered for a possible modular revamp of pieces. (Rust is a general-purpose, multi-paradigm programming language)
2:54

👀Decisions are being made today. If restarting the #XRP ledger from scratch, Ripple CTO David Schwartz discusses using "Rust" is definitely talked about. Proposals from an outside company are currently being considered for a possible modular revamp of pieces. (Rust is a general-purpose, multi-paradigm programming language)

🌸Eri ~ Carpe Diem

221,605 views • 1 year ago

Why is Rust different than many/most programming languages? Alice Ryhl works on Google's Android Rust team, is a Rust language team advisor, and is a core maintainer of Tokio (the most widely-used async runtime in Rust) Timestamps: 00:00 Intro 04:09 Tokio: an overview 05:11 What Alice likes about Rust 12:48 Rust for TypeScript engineers 13:51 Moving from C++ to Rust 14:34 Memory safety 18:12 Garbage collection tradeoffs 21:46 Ownership, references, and borrowing 26:59 Unsafe in Rust 31:21 Crates and Cargo 35:55 Language design and RFCs 43:02 Building new features 46:30 Editions vs. versions 49:47 Getting paid to work on Rust 51:27 Contributing to Rust 53:03 Rust in the Linux kernel 55:45 AI use cases for Rust 1:01:35 Learning Rust 1:03:54 Book recommendation Brought to you by: • Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. • Sentry – application monitoring software considered “not bad” by millions of developers Three things worth knowing about Rust: 1. Rust was designed to turn implicit failures into compile errors. Where other languages allow you to forget something, Rust makes an omission into a compilation error for things like null checks, uninitialized variables, or error propagation with the ‘?’ character. If you mess something up, it’s almost certain your program will not compile. If it does, at the very least you should see a lint warning. 2. Refactoring in Rust is safe and easy, thanks to the compiler. Alice: “I change a return type or struct field, then just fix the compiler errors until the compiler stops shouting. And then once I’ve done that, I’ve updated every place I need to update.” Rust’s focus on correctness makes refactoring it more straightforward than dynamically-typed languages and Java-style typed ones are to refactor. 3. “Editions” allow Rust to make breaking changes without ‘breaking’ anyone’s code. Rust editions (2015, 2018, 2021, 2024) can be mixed freely across crates. A library on the 2021 edition works seamlessly with a binary on the 2024 edition. This is how Rust evolves syntax (like adding async/await as keywords) without forcing an ecosystem-wide migration. Thanks a lot, Alice for this great discussion! And for your work on Rust.
1:05:52

Why is Rust different than many/most programming languages? Alice Ryhl works on Google's Android Rust team, is a Rust language team advisor, and is a core maintainer of Tokio (the most widely-used async runtime in Rust) Timestamps: 00:00 Intro 04:09 Tokio: an overview 05:11 What Alice likes about Rust 12:48 Rust for TypeScript engineers 13:51 Moving from C++ to Rust 14:34 Memory safety 18:12 Garbage collection tradeoffs 21:46 Ownership, references, and borrowing 26:59 Unsafe in Rust 31:21 Crates and Cargo 35:55 Language design and RFCs 43:02 Building new features 46:30 Editions vs. versions 49:47 Getting paid to work on Rust 51:27 Contributing to Rust 53:03 Rust in the Linux kernel 55:45 AI use cases for Rust 1:01:35 Learning Rust 1:03:54 Book recommendation Brought to you by: • Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. • Sentry – application monitoring software considered “not bad” by millions of developers Three things worth knowing about Rust: 1. Rust was designed to turn implicit failures into compile errors. Where other languages allow you to forget something, Rust makes an omission into a compilation error for things like null checks, uninitialized variables, or error propagation with the ‘?’ character. If you mess something up, it’s almost certain your program will not compile. If it does, at the very least you should see a lint warning. 2. Refactoring in Rust is safe and easy, thanks to the compiler. Alice: “I change a return type or struct field, then just fix the compiler errors until the compiler stops shouting. And then once I’ve done that, I’ve updated every place I need to update.” Rust’s focus on correctness makes refactoring it more straightforward than dynamically-typed languages and Java-style typed ones are to refactor. 3. “Editions” allow Rust to make breaking changes without ‘breaking’ anyone’s code. Rust editions (2015, 2018, 2021, 2024) can be mixed freely across crates. A library on the 2021 edition works seamlessly with a binary on the 2024 edition. This is how Rust evolves syntax (like adding async/await as keywords) without forcing an ecosystem-wide migration. Thanks a lot, Alice for this great discussion! And for your work on Rust.

Gergely Orosz

52,183 views • 4 months ago

Grok Code Fast 1 is versatile across the full stack and is particularly strong at TypeScript, Python, Java, Rust, C++, and Go. Using Grok Code Fast 1, Danny Limanseta built the following game in a day.
0:58

Grok Code Fast 1 is versatile across the full stack and is particularly strong at TypeScript, Python, Java, Rust, C++, and Go. Using Grok Code Fast 1, Danny Limanseta built the following game in a day.

SpaceXAI

1,076,168 views • 1 year ago

Linus Torvalds says that C is king for OS development due to its efficient hardware interaction and the ability to predict the assembly language output of C code.
1:18

Linus Torvalds says that C is king for OS development due to its efficient hardware interaction and the ability to predict the assembly language output of C code.

tetsuo

3,010,229 views • 1 year ago

The Art of Rust is a beautifully crafted, full-colour hardback book that highlights every element and the artistic journey of Rust. 🧠🎨📖 Get yours here:
0:26

The Art of Rust is a beautifully crafted, full-colour hardback book that highlights every element and the artistic journey of Rust. 🧠🎨📖 Get yours here:

Rust

52,338 views • 6 months ago

C to A : u don't have to worry about me C to T : i think it's the degradation, don't tell the others and folks this is why Cloud only lets Tifa ventured his subconscious, the only person he can openly be vulnerable to
0:31

C to A : u don't have to worry about me C to T : i think it's the degradation, don't tell the others and folks this is why Cloud only lets Tifa ventured his subconscious, the only person he can openly be vulnerable to

Dear girl Tifa

12,132 views • 16 days ago

RUST ANYWHERE — Rust Mobile Rust Mobile Closed Beta begins December 11. Registration is now open for the first handheld test of the iconic survival experience. Gear up, build up, and dive into a reimagined Rust world, fully optimized for mobile. Sign up here: #RustMobile
1:33

RUST ANYWHERE — Rust Mobile Rust Mobile Closed Beta begins December 11. Registration is now open for the first handheld test of the iconic survival experience. Gear up, build up, and dive into a reimagined Rust world, fully optimized for mobile. Sign up here: #RustMobile

The Game Awards

127,739 views • 10 months ago

In Rust, error handling is opt-out, not opt-in. Alice Ryhl (Rust for Android at Google, Rust language advisor & Tokio maintainer) explains: “The other thing I think is quite good is error handling. So on one hand, Rust doesn't really use exceptions, so it actually returns the error as a value. So you return a value that's, using an enum, either the result or the error. And the way this is done is that there's an operator `?` - so you write: my_function and then a question mark at the end - which means if this function fails, return the error. So it's really easy to handle errors but it's not serial characters like it is with exceptions, so it's explicit. On the other hand, if you forget to put the question mark, that's a compilation error. So you have to check it, and of course you can also have it manually, but the point is it's this idea of there are these things where you write some code and there's some implicit error condition you didn't think of and now you just took down your server or something.”
1:13

In Rust, error handling is opt-out, not opt-in. Alice Ryhl (Rust for Android at Google, Rust language advisor & Tokio maintainer) explains: “The other thing I think is quite good is error handling. So on one hand, Rust doesn't really use exceptions, so it actually returns the error as a value. So you return a value that's, using an enum, either the result or the error. And the way this is done is that there's an operator `?` - so you write: my_function and then a question mark at the end - which means if this function fails, return the error. So it's really easy to handle errors but it's not serial characters like it is with exceptions, so it's explicit. On the other hand, if you forget to put the question mark, that's a compilation error. So you have to check it, and of course you can also have it manually, but the point is it's this idea of there are these things where you write some code and there's some implicit error condition you didn't think of and now you just took down your server or something.”

The Pragmatic Engineer

52,059 views • 4 months ago

The legend of Namibia. Mr "it is what it is" with his bulletproof Jeep. What a guy. C Boss-WP
0:45

The legend of Namibia. Mr "it is what it is" with his bulletproof Jeep. What a guy. C Boss-WP

Ndilula

28,131 views • 1 year ago

Programming Isn't Math, It's Linguistics. Compilers and Humans have the same problem. We're all terrible at understanding each other. Join me for some formal language theory, a lot of C++, and some "recreational" insults.
0:58

Programming Isn't Math, It's Linguistics. Compilers and Humans have the same problem. We're all terrible at understanding each other. Join me for some formal language theory, a lot of C++, and some "recreational" insults.

LaurieWired

984,816 views • 11 months ago

The end of apps is near. Programming is changing right before our eyes. Let's break down what Linus Torvalds, the creator of Linux, thinks about AI and programming.
19:45

The end of apps is near. Programming is changing right before our eyes. Let's break down what Linus Torvalds, the creator of Linux, thinks about AI and programming.

Matthew Berman

40,790 views • 2 years ago