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

Channel:ChariotSolutions · Length:55:07 · Published:2019-05-09 · Views:366900

Watch on YouTube

Summary

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.

Why HN recommends it

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

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

Programming language design · C, C++, Rust, Go & systems languages

Subtitles (excerpt)

so you are in the talk rust a language for the next forty years my name is Carol nickels or Golding it's short-circuits I will answer two nickels quicker but you can also call me Carol building if you want I'm Carol's ten cents on all the various platforms I have a lot of links in my slides so if you want to be able to follow up on references and check out some more things this short link will take you to a repo where there's link to view the slides on the web and the readme has just the links pulled out as sort of alluded to in the intro I'm the co-author of the rest programming language book which is available for free online and available in print from no starch press I'm also a co-author on a Manning live video series called rusted motion that's in early access right now and thanks to Manning I have three codes for free access to this rest in motion so the favorite my favorite three questions are going to get access to this so please ask wonderful questions on the slide slide Oh question asking platform I am also a co-founder of integer 32 the world's first rust consulting company and I am an organizer of rust belt rust a regional rust conference this year we're going to be in Dayton Ohio on October 18th and 19th and I'm on the rust core team so if

On 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] [VIDEO] — norman784, 2024-03
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… — asoneth, 2021-12
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] [VIDEO] — lsllc, 2021-05

Related videos