@UNgineering
"even a javascript developer can understand" apply cold water to affected area.
@JunaidulIslamJarif
wow a unbiased RUST video
@ivlis.w
I'm lately considering to learn Rust, not because I specially like it, but because most of the projects I like use it, and I may want to contribute to them in the future
@bytejuggler
In 3:16 (and I've not yet watched the entire video) you just explained ownership to me in a way that is crystal clear to me, and I'm not yet a Rust programmer. Thank you. That makes perfect sense. Couldn't be clearer.
@RenderingUser
For people who come from other languages, my number 1 suggestion is always half-hour to learn rust article by fasterthanlime
@elael2
I haven't seen "free" in a C++ code base in years.
@MauroPanigada
9:10 btw, the final keyword in Java does not disallow the ability to mutate the state of an object. Doing profile.setName("another name") is legal even when profile is marked final. If a class has public setters (or other methods which mutates the object), you cannot avoid a callee to use those methods. Java is very weak for this kind of things.
@gavinfuchs
PS: Worked on java code for the past 15 years professionally. Had no Nullpointer since 10 years. So it also always depends on the "quality" and "style" of your code :D
@porky1118
10:20 This "Allow less by default" mentality of Rust is great. I try to use it when designing my own systems.
@marcusdowning
I want to send this video back in time 40 years (presumably on a VHS) and make the language designers of the era watch it 10 times.
@fallout__boy1130
Very good intro to rust, thanks a lot, this is super valuable.
@untilwemeetagain_
At 5:07, is the user4 passed to update_name supposed to also be referenced inside (i.e., user4.name = name)?
@ep7503
Rust in 2 seconds : Fe2O3
@enespinar9711
"Even the Js developer can understand it"😭😭 We're not python developer
@ねつてつ
2:32 Oops, there is no `user` variable in `print_name` function, but `user3`
@Nellak2011
Great explanation. ❤
@PetraleiTanyl
Your description of prototypes ignored panics! In fact it is explicitly not true that if your rust compiles it's free from crashing.
@SergiuszRoszczyk
So are we GUI yet? Nasty rants aside - I give Rust a try for my low level project that I need to run on a Cortex M3+ class micro. Initial experience with writing system independent core was nice, integrated testing and borrow checker which made me rethink few design choices. A matter of taste but doable. Then the hard day came in. I need to run my code and also monitor the state of simulated registered (plain memory array) using DMA and peripherals provided by the platform. RP2350 support - non existent, bigger ST micros - not that much. I spent few weeks facing different walls with rp_hal and Embassy, to get to the point I need to write my own support for DMA and unsafe borrow checker. Also PIO support and macros were broken and didn’t work as in docs. In the end I asked myself a question - should I write my own HAL on top of chip I don’t control (vendor just gives it to me) or rely on proven, vetted and stable HAL in C? In the end project went using C language and a core library can still be tested by importing it to Rust or Python for testing and even running on a desktop PC to separate hardware concern and library concern.
@jiniwarable
Actually jokes aside I think Rust is a solid language. I have been learning Rust for the past months and I think I like how the Rust handles different stuff.
@letsgetrusty