Rust: A Language for the Next 40 Years - Carol Nichols
ChariotSolutionsCited 3× on HN, 2021-2024
367K views · 7 years ago · talk · dated
Carol Nichols' Philly ETE 2019 talk on what makes Rust unique. It covers memory safety, how editions let the language evolve without breaking code, and who relies on Rust in production.
Cited as a talk about Rust's long-term outlook, and as the source of the rail-safety analogy for software safety.
1:38:57Carbon Language Successor Strategy: From C++ Interop to Memory Safety - Chandler Carruth - CppNow 23
CppNow
24K views • 3 years ago
1:29:49Going Native 2012 Keynote Stroustrup
savage309
33K views • 14 years ago
48:46Rust's Journey to Async/Await
InfoQ
90K views • 7 years ago
1:33:23Crust of Rust: Lifetime Annotations
Jon Gjengset
299K views • 6 years ago
3:03:54The Why, What, and How of Pinning in Rust
Jon Gjengset
87K views • 7 years ago
48:19GopherCon 2014 Inside the Gophers Studio with Blake Mizerany
Confreaks
8K views • 12 years ago
59:26The Go Programming Language
Google TechTalks
406K views • 17 years ago
1:00:29Google I/O 2012 - Meet the Go Team
Google for Developers
108K views • 14 years ago
1:09:18Is It Time to Rewrite the Operating System in Rust?
InfoQ
310K views • 7 years ago
1:05:56Lang NEXT 2014 Panel Systems Programming in 2014 and Beyond
25msr
3K views • 8 years ago
59:48The Road to Zig 1.0 - Andrew Kelley
ChariotSolutions
168K views • 7 years ago
29:25Rust NYC: Jon Gjengset - Demystifying unsafe code
Rust Programming Language
27K views • 6 years ago
12:31OSCON 2010: Rob Pike, "Public Static Void"
O'Reilly
119K views • 16 years ago
56:36GopherCon 2014 Opening Keynote by Rob Pike
Confreaks
38K views • 12 years ago
1:55:24Ideas about a new programming language for games.
Jonathan Blow
530K views • 12 years ago
0:27Rob Pike about the target group of the Go programming language (golang)
f8C4G86p KbqEFe47
7K views • 6 years ago
1:07:00Sydney Golang Meetup - Rob Pike - Go 2 Draft Specifications
Macquarie Group
57K views • 7 years ago
34:41Microsoft is Getting Rusty: A Review of Successes and Challenges - Mark Russinovich
Rust Nation UK
46K views • 1 year ago
32:24RustLatam 2019 - Without Boats: Zero-Cost Async IO
Rust Programming Language
55K views • 7 years ago
54:55Dconf 2014 Day 2 Keynote: The Last Thing D Needs -- Scott Meyers
The D Language Foundation
19K views • 8 years ago
3 comments from Hacker News
I think Rust team would still have a very small stdlib even if they have more funding, here's a talk[0] where they aim to be relevant for the next 40 years, in that time span there would be a lot of changes and to be backward compatible, you cannot have features in your stdlib that will be irrelevant or change in the next 5, 10, 15, 20 years. [0] ▶ this video
In my opinion, what has been most harmful for evolution of the software engineering profession is the tendency to blame individual developers for not being infallible instead of fixing chronic failures in tooling, processes, and funding. The medical profession, aviation, even rail transportation [1] have all progressed past the point where avoidable failures are entirely the responsibility of the individual. Of course, there was resistance in those fields as well because some considered themselves an "above-average" doctor or pilot who didn't need safeguards, checklists, union rules, or laws. But it empirically improved outcomes. [1] ▶ this video
FYI, Carol Nichols mentioned this in a Rust video [0] and I thought it was pretty interesting! (yes, previously submitted to HN, but long ago with little traction so I think this is within HN guidelines). [0] ▶ this video