It can’t be the best unless it does all that, but was simple. Instead it’s complex with a steep learning curve. That’s not a small issue, people don’t run companies don’t understand the value of being able to move quickly.

It is a big claim, going forward seems like python will be the best programming language

The only headache I have about rust is it’s slow to compile🥲 I sometimes loose interest in the project because of slow compile times and end up using c++

Awesome, thanks

"Ok, so hear me out on this: Rust" _mixed reaction from the crowd_

A lot of folks memory issues can be simply resolved by using a std::vector in C++.

how does this apply when using async though?

what is ti with rust programmers i've never seen similar weird community of a programming language, i've used rust for 2 years along side C/python and Go recently, it is : a simple language + "best practices" enforced by the language anyone can by choice implement those concepts in any other language . for example all languages have mutex, rust enforces mutex wrappers on mutables to avoid lock-ins (you forget to unlock) the same wrapper could be implemented in any language in 10 lines of code only rust ENFORCES IT ON YOU and calls it a feature, get over yourself just learn the concepts and use any language you feel productive using (5% performance increase doesn't matter in 99.99% of your projects) by the way none of rust "best practices" are invented by rust team all are known techniques from 70's and 80's long before they were even born

you kinda sound like chris griffin

but bash isnt an real progaming language

Very clear and understanding .. you must do more videos like this

i dont know C . and simple explain was above my head

I don't really get the obsession with Rust's ownership model, yes its cool and almost always promises the programmer to handle memory deallocation in the end of the scope, but... combined complexity of other things in the language like enums that can hold values , Heap based types (Rc, Box,Arc,etc.) or Macros make it unbearable to quickly develop things. Problem that nearly everyone point at, of: "bug because of use after free" or "forgot to free() in C, unsafe!!!!" aren't as much of a deal as the unnecessary complexity of doing literally anything in the language. It could've be the case, if there where no debug tools, valrgrind or bounds checking in all of the system programming languages for decades. I doubt that you need majority of the features (even core one) in rust to make "safe software".

Very informative! Love ❤️ it!

Love 💗 this. Great job Jacob! With both the video and your speech! 🙏🏼❤️🙏🏼

Rust did not introduce anything new, these things like ownership and linear types has been talked about for 30 years, so stop making bullshit videos just to promote a language. Here's one old paper for example and there are many more too. citeseerx.ist.psu.edu/document?repid=rep1&type=pdf&doi=24c850390fba27fc6f3241cb34ce7bc6f3765627

Rust is a joke!

Nitpicking, but rust wouldn't pop arr from the stack after the move. It's the compiler that marks arr as no longer valid. It's a compile time check, not a runtime action.

you used single quotes for variables...

This deserves far more than 5000 views. Excellent video!

Bro you're the best 🫶 This is the best video by far that I could find to understand about executables.

Awesome video and I just subscribed! (Some feedback is that the transitions where letters scattered or rearranged was annoying. It works when expanding an acronym but otherwise it looks like dyslexia)

You should claim rust is the best if you can compare it with something like Zig, I believe zig has the best of the two worlds

gg bro

You’re so cool

Love you, I’m so proud of you and can’t wait to see what’s next!!

"I don't know if it was never explained to me". Story of my life.

Really love the way how we end the if loop with "fi" lol

Generally well explained but left out are the MANY corollaries of Rust's philosophy such as standing on your head to get two objects that point to each other and the difficulties inherent in graphs. That you have to drag in special crates just to have a mutable global. New concepts entirely like lifetimes need to be understood, etc., etc.. I realize there are solutions to all this, but Rust requires a lot more out of the programmer than C++ does - it just does. I also realize that most Rust programmers would say that's a good thing and most of the time I'd be with them on that opinion, but to leave all this out will really not describe to a C++ programmer the difficulty of adjusting to Rust. This makes it seem like ownership is a no-brainer and "that's all there is" when, in fact, the devil's in the details.

I love that `esac` is just `case` backwards and `fi` is just `if` backwards.

Quote your variables

Bash has to be the most usable esolang. I've never been able to write a nontrivial bash script without looking up a bash cheatsheet.

there’s something about closing a block with the mirror image of the opening keyword that really appeals to me

the bourne ultimatum

Domain specific languages are cool sometimes

yuck! Bash's manual is just 300 pages of special cases!

It's cool!

someone pls explain to him Rust does not protect from memory leaks in the first place..

Rust Probaganda be like C is Old C++ is Bla bla bla and in the last minute they start talk about Rust and then the vedio end

C++ Smart pointers: I don't exist**

isn't this just like an std::vector<int> though?

Thank you for the great video!! what software do you use to make such illustrations?

This concept is called RAII and you could do it in C++ years before Rust existed

C++ works exactly as described in the video 😂

you can run popen("/bin/ls -lh") and read its output in stdin

Great video btw actually made me so curious that i would like to learn more about rust

So doesn't Smart Pointers in C++ also solve this particular problem of memory leak when variables are going out of scope? Like if we have a pointer and enclose it in a class then if it goes out of scope it's destructor will be called which will initiate the cleanup code required to free up the memory. Is it not a good enough solution or am i missing something?

Wait... but c++ does pretty much the same things. Only difference is = copies by default and you have to explicitly std::move

clickbait

Surely it is because I’m an old fashioned C/C++ programmer and I can’t still see the beauty of this ownership paradigm, but right now I can only think about how annoyingly painful would be for me to try coding about anything in Rust, I already have a headache just from thinking about it. I can definitely see the advantages of of the compile time analysis and strict memory management Rust provides, but I’m afraid it comes with a cost in flexibility and usability that may be too high for certain situations.