Rust is not a faster horse

A lightning talk showing you how while other languages are satisfied to iterate on the state of the art, Rust revolutionises it.

Corrections are in the pinned ERRATA comment.

CREDITS & PROMO
My name is Tris Oaten and I produce fast, technical videos.

[NoBoilerplate]

ERRATA

3:51 I line 3 in the second code snippet is supposed to be `b = "newname"` (thanks VVill!)
1:02 Go is not object oriented, my mistake (I suppose I saw 'interfaces' and extrapolated from there) I'm delighted

[Scriabin_fan]

Alright that's it, I'm learning Rust. That's the first time I've ever felt happy reading a compiler error.

[wkeee]

“A fast executing language that crashes all the time is like a supercar… that crashes all the time” -0atman 2022

[micycle]

"Rust has an algebraic type system, and if you know what that is, you already know you want it in your language." no statement exists that is more perfect

[tjgdddfcn]

To anyone starting out with rust: dont let the immature ecosystem scare you from using it . Unless you’re writing extremly critical enterprise software, the most popular library for the thing you want to do will have everything you will ever need

[_remblanc]

Even if you do like dynamic language’s ability to just set something without specifying the type, Rust also lets you do that through type inference, which is pretty much having a cake (being able to define stuff without worrying much about specifics) and eating it too (it’s still static typing and you get all its benefits)

[raddude]

I've started my first project in Rust because of you! Thanks for spreading the word about Rust

[WizardofWestmarch]

Go cannot be a better c++, a language with a GC is fundementally solving different problems. Otherwise you could argue Java or c# is a better c++.

[efronlicht]

Thank you. Go, Rust, and Zig are not enemies. They are friends!

Its interesting that you see Go as a replacment for C++. While it was designed as one, I tend to use Go where 10 years ago people would have used scripting languages: simple CLI apps, webservers, small tools. I also lean towards it for prototyping or 'throw-away' code, because the Go compiler's incredible speed makes iteration faster there.

I use Rust where I need performance or safety and can afford to write from scratch. When I write Rust code, I'm confident that it's correct. In general, it's my preferred language for hobby projects. Rust also has best-in-class documentation, dependency management, and publication tooling. It's my personal favorite, so that's a tiebreaker.

I don't use Zig (much, yet!), but when I do, it's where the pre-existing infrastructure expects C and C's conventions (i.e, in the world of device drivers, syscalls, and OS internals). Zig is still a bit immature, but the project is rapidly improving. Like it or not, the world we live in is built on 50 years of C, and not everything can or should be rewritten in Rust. Zig helps bridge that gap. The Zig community is incredibly generous w/ their time and expertise, too. They've helped both the Go & Rust projects, despite being significantly smaller.

[grant]

“A fast executing language that crashes all the time is like a supercar driven by Richard Hammond” -Jeremy Clarkson

[imnemo]

_"Rust might not be the language you wanted, but it might be the language you need"_ ~ Great Explanation

[TheCoderCareer]

Thank you so much for creating easy to understand, digestible and clear videos on Rust. Much respect.

[DaDa-grcy]

Rust community is very lucky to have people like you. Keep up the good work!

[fders]

I used to be primarily a C programmer, a little bit of x86 ASM, and C++. I remember seeing videos like this and "C turned 50 today, so I decided to learn Rust" by Low Level Programming, and wondering what all the fuss was about. I eventually decided to give it a try, and it quickly became my favorite programming language. To me, it feels like what C++ should have always been. I know you made another video about this, but it really feels like in Rust I can focus on actually solving a problem instead of remembering to check for nullptr and use copy methods, all without introducing any runtime overhead. I write some code, cargo check, cargo build, then move on to the next problem. I don't need to study a method for an hour to make sure I didn't just implement RCE.

[chrissaltmarsh]

I love this stuff. I'm retired, now, but I used C back in the day, close to the metal, for physics experiments. Before that it was assembler and sometimes machine code.
But C does give you serious foot wounds on occasion.
Rust has proper ideas to stop that while you still have real control over the runtime.
(In my case, small computers/microcontrollers, networked, doing monitoring stuff).

Great series, keep it up.

[jongeduard]

Hi! There are 2 things in Rust that I personally like very much as well:

First of all literally any compound statement is actually just another expression, returning the result from a final expression inside it when that subexpression is not followed by a semicolon. And even if it hasn't such an expression, it still returns a value, namely the Unit type, which is an empty tuple. There's no void return type.
This is non-typical for C family programming languages, and comes from functional language influence.
It's something that I really mis in C# for example, which is also a very great programming language by the way (I work with it for 20 years already).

Second thing that I like is that Rust's object oriented way of programming chooses composition over inheritance strategies, which is good, because inheritance causes many problems.

[TimePlaysLifePasses]

Wow. This guy’s talking so well about a compiled language that I feel he’s a script writer!
So many statements that would be great chapter names !
Subscribed.

[MegaCashB]

What do you mean Go is a better C++? Go has a Garbage collector. I would say Go is more of a better faster Python/Javscript thing, because it's still slower than C++.

[MatteoGuadrini]

As a python developer, typing every variable is very difficult work. But every line written in Rust, I think that it is very beautiful language. I love Rust and Rust love me.

[MechMK]

I've always said, statically typed languages make reading code much easier, because I can be sure, that the things I see will always be that way.
Dynamically typed languages make writing code much easier, because you can get things done without thinking too hard about the "what if's".

Experience tells us that programmers spend much more time reading code, than writing code.