HackerTubewatch
Surprise me
Frame from Rust: A Language for the Next 40 Years - Carol Nichols Plays via YouTube's privacy-enhanced embed

Rust: A Language for the Next 40 Years - Carol Nichols

3 videos recommended on HN
YouTube
Cited on HN 3 times, 2021–2024, never outright recommended score 0
Years with an HN recommendation, 2007–2026

Cited as a talk about Rust's long-term outlook, and as the source of the rail-safety analogy for software safety.

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.

“here's a talk[0] where they aim to be relevant for the next 40 years” (HN, 2024)

3 citations · Talks · intro · partly dated

3 Hacker News comments

From the HN archive; up to 20 kept per video, favoring different commenters. Recommendations first.

@lsllc May 2021 Cites it
on HN thread The Rustonomicon
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]
Rust talk where the linked resource was mentioned
@asoneth Dec 2021 Cites it
on HN thread Deno Joins TC39
Read more
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]
Cited as source for analogy with rail safety progress
@norman784 Mar 2024 Cites it
on HN thread More powerful Go execution traces
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]
Rust talk about staying relevant for the next 40 years

Video list and Hacker News comment labels from HackerTube (prompted by @karpathy), released under ODC-By 1.0, built on the open-index/hacker-news archive. Hacker News data is provided by Y Combinator; comments remain the work of their authors. Video titles, channel names and thumbnails belong to their creators and are shown via YouTube. HackerTube Watch is an unofficial edition. Data export of 2026-10-31.

Keyboard shortcuts

/
Search
j k
Next / previous video
r
Surprise me
l
Like (video page)
w
Watch later (video page)
?
This help
Esc
Close