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

Learn what makes the programming language Rust a unique technology, such as the memory safety guarantees that enable more people to write performant systems-level code. Hear about how Rust Editions evolve the language and the compiler without breaking existing code. See who’s trusting Rust for critical products today. Join us on Rust’s journey to the future.

[chaitanyamolli]

I think the presenter is honest, down to earth and real. No bullshit. I'm an experienced programmer in C, Golang, Dart and other scripting languages. What she is saying, makes lot of sense. She convinced me to dig deeper into Rust language

[MadBroStudio]

I just like that rust has a package manager. Makes making things so much easier, especially for web development.There's no other low level language that has a package manager

[davidxu]

The most headache bug is not when you cannot get the code running, the most headache is: the code runs into problems only once when running thousands of times. Rust is the future!

[addmoreice]

A day after this was posted and it was out of date in regards to private crate hosting now existing. That's a good sign. Developments are constantly moving forward.

[nicholaskeyes]

I love all the people missing the point of the talk, and then complaining that a specific technical feature wasn't discussed.

[crtune]

I personally believe that thorough and significant problems warrant seriously considering the BASE DESIGN. This sounds like the reason for a Rust. I will definitely be looking into this language (while I learn all these others too!).

In a side bit of trivia, my dad made his living as a corrosion engineer (thus rust was arguably his business; though he was fighting corrosion in water systems).

[BernardoSOUSAstudent]

I was wandering, what?! Trains?" Then you said "safe by default". I immediately understood the point :)

[BKPrice]

Ironic that a man named Coffin would be concerned about railroad deaths.

[rkk]

Love her sense of humor: "let's make new mistakes " ;-)

[leonk]

nobody: ...

Rust language team: hehehe we have ::<> thats a *TURBOFISH*

[moonsettler]

i can totally see senators passing a bill banning pointers altogether after the first minute you try to explain memory safety to them just to get away from hearing more of it.

[thanatosor]

The "unsafe" keyword in Rust is like the plot-twist in every movies, where the story sudden change, or your program suddenly crash.

[pamus]

Rust is/will be successful for common-sense reasons....no revelation, nothing special.
As a former C user, I'm never going back.

[jhpratt]

Saying you'll never break compatibility is a bit misleading, even with the given caveats. There have been breaking changes slipped in, even without an RFC.

[brandonlewis]

I like the comparison with Brakemen vs. AirBrakes. Thanks sharing that history, it's fascinating. And also, thanks for sounding the alarm. Software industry is, ironically, reluctant to change its own ways.

[shlemekian]

Loved this talk. Especially how open she was about Rust's current shortcomings, that is an excellent sign for anything. With all the current popularity, you could easily just evangelize the hell out of it and have everyone in the conference cheer, so I love that.
I have no need to use Rust in my current development role, but I may have to pick it up for fun soon. I'm Rust-curious now

[GregWoodsLancs]

I'm just starting out in Rust, coming from high level languages, and some simple-ish Arduino level C++. Rust certainly seems like the right ways to go. Great video, gave me some reassuring background, as well as some useful technical detail.

[enverhoxha]

There are so many bugs that can be statically avoided... And rust makes very nice compromises between safety and usability.

[vainglories]

Her energy, enthusiasm, knowledge, optimism, and open-mindedness combined are nothing short of adorable. As someone equally in the business of building a potential disruptor of status quo, the part at min 46:51 particularly resonates with me: "Let's make new mistakes!". I like the sound of that mindset

[yzhang]

I'm a Ruby and Go developer. Have learned Rust but haven't done andy real project in it yet. My understanding is that Rust is best at its memory security and performance. But the overhead on programmers is not trival. Meanwhile the goroutines and channels in go are really gold. Rust can do silimar things but not as easy. So for the next 40 years, there will be new languages which would make both go developers and current Rust developers, even including Ruby developers, to smile in front of their keyboard.