This talk was recorded at NDC TechTown in Kongsberg, Norway. #ndctechtown #ndcconferences #developer #softwaredeveloper    

Attend the next NDC conference near you: 
https://ndcconferences.com
https://ndctechtown.com/

Subscribe to our YouTube channel and learn every day:   
/      @NDC 

Follow our Social Media!

https://www.facebook.com/ndcconferences
https://twitter.com/NDC_Conferences
https://www.instagram.com/ndc_conferences/

#rust #keynote #api 

Rust users are often very enthusiastic about their language. Sometimes annoyingly so. Where does this enthusiasm come from? There has been a lot of talk about Rust memory safety, but this does not explain why users are so positive about the language.

Rust users will sometimes try to explain how Rust programs seem to "just work". Is there something to this? Where does this come from? And could this explain part of the enthusiasm?

It could be argued that Rust is not really about memory safety specifically, but more about making incorrect programs in general harder to write.

This talk will try to cover some of the language features and techniques behind this, like:
- The strong type system
- Strongly typed error handling
- The lack of implicit conversions
- Good API design for types like Options and Result
- Sum types and pattern matching
- The typestate pattern

NDC Conferences

Rust's primary value isn't memory safety but correctness through its type system. The language uses enums with data, pattern matching, and the Result type to catch errors at compile time rather than runtime. Features like the question mark operator for error propagation, move semantics by default, and consuming methods enable the compiler to enforce correct API usage. This strong static typing reduces the need for unit tests, makes refactoring safer and faster, and ensures that code that compiles is more likely to work as intended.

Keynote: Rust is not about memory safety - Helge Penne - NDC TechTown 2025