The best quote. My honest advice for people serious about Rust game devoplement: Forget about the engine solutions. They are unfinished and untested in large scale commercial productions. You will hit a wall easier as the needs of your game grow compared to Unreal / Unity. Instead, setup your own wgpu rendering and Rapier physics (if you need physics). There's nothing wrong in studying the engine solutions' specific parts such as bevy's skeletal animations, just keep the full control to yourself. It's more work and effort, but maybe if you are aiming for quick commercial game release, Rust is not the best language to develop with at the moment.
Actually really good take. If you learn the biggest pitfalls and struggles and think you can tolerate them, I don't think you're gonna mind the rest of the languages.
@@sudiproy4413 it's a reference from a video Interview with Senior JS Developer from this channel in case you didn't get the joke. Well, actually i wouldn't recommend it either
Let's be fair -- they avoided the messes of inheritance. Or ml modules. And they don't have higher kinded types (well, they have GATs which let you do the same thing).
@@TheMohawkNinja llvm optimisation pipeline for release builds takes ages and then for incremental builds the long part is always gonna be the linking step (you can substitute a better linker depending on platform, e.g. mold for linux) because most linkers we have are archaic monstrosities that dont parallelise well and that doesnt play nice with the deluge of object files rustc will spit out for incremental builds
It's incredible to me how well you "get" the languages you parody. Like, it's clear you understand the inner culture and the most complex concepts of these languages.
Honestly facts. I sometimes see rust analyzer spend 2 minutes trying to compile the entire repo and itll sometimes shit on PROC MACRO NOT FOUND. ALSO L LOSER I DONT KNOW WHAT THIS "SeRdE SeRiaLize and DeSerIaLizE" IS. Re run it. Teehee, i made an ooosie, ur code is fine don'r hate me uwu
I don't get that meme, because if you use a powerful enough machine compile times in Rust are not a problem. Even if the crate takes longer than you want to compile, you can just split it into smaller crates. Moreover, I have a project where both Rust and JS ecosystem is used, and producing a JS bundle takes like 10x more time than it takes to generate the WASM bundle part of it.
first what I had to do when tried Rust first time - is force unsafe because else multithreading communication with external hardware wont work so funny xD
For those not getting the "write an operating system in three weeks" reference, Ken Thompson wrote the initial version of Unix in three weeks. One week for the kernel. One week for the file-system. One week for the shell. In assembly.
Especially that one who constantly makes subtle changes in browser logotype. Separate one with GNOME designer (I personally hate them and would be glad to see satire about GNOME approach).
" after a well managed , well-mannered discussion , that will make everyone unhappy " " im fully oxidized at this point " incredible video , such great specific examples
@@JMurph2015 Nah, it was about *another* flamewar about what we should call the keyword for early-returning inside try-blocks, IIRC. Eventually the lang team decided "You know what, fuck it, let's call it the "yeet" keyword until we have a working implementation, that'll stop the bikeshedding". So now "yeet 64" is a valid Rust statement in nightly.
"Lots of jobs for us, most are for startups to do some blockchain stuff.. and then go bankrupt" life is always on the razors edge when you are a Rust dev
I shit you not, my old software manager, when comparing Rust and C compilation times, told us that "C's compilation is blazingly fast". That phrase stuck with me and now I feel like he was making an inner joke while trashing Rust in some aspect.
I have seen this 3 time. It is so well done, very high effort. Great job! Their are so many extremely funny jokes and the delivery is executed so well.
😅 For real, the funniest line, apart from I joined a couple of start ups in this month or I wanted to compile my personality into a crate... actually too many lool
@@tui3264 To be fair, this is also true for all the programming languages, the number of games you have is usually half the the number of game engines people tried to make and failed hahahahaha
That situtation is actually sensible and interesting. Graphics APIs (OpenGL, Vulkan, Direct3D,...) have the following challanges: 1) things are checked at runtime and *only* at runtime 2) exhaustive testing is impractical (you need the combinations of all physical GPUs and all drivers) 3) the API has a lot of variability (different implemented featuresets, different API versions,...). All in all, this is a hot mess for graphics & gamel developers. If some technology were to tame this (and prevent lots of grey hair for game developers), this would probably be worth billions and billions of dollars. Personally, I'm not sure that graphics APIs can be tamed with Rust without constraining the API functionality too much (there is just too much variety there...). TOTOH if these projects actually succeed, it would prove Rust to be a tool of truly monstrous powers...
@@marcossidoruk8033using any language for game or game engine development is always *eventually* painful, when you get big enough to actually run up against the hardware. Using Rust is making the assumption that the average to peak suckage will be lower than other languages. You probably are thinking more about the scripting side, but you can host a runtime, including new Rust-flavored scripting languages if you want that hot loading experience.
- Yeah, but nobody knows Haskell. We're all looking to learn Rust - Come back after you've learned Haskell coming to Rust from Haskell, I confirm that this really helps
This is just impossibly good! :-)) I have about 30 years experience with programming, I started when Pascal was still big, so I know a think or two about the languages. So I tried Rust, picked just a simple hobby project (a curtain controller logic) and after two weeks I just couldn't finish it. Than I freaked out and returned to C++ and was done within a couple of evenings. Rust's learning curve is just... too much. Although a bunch of ideas are interesting.
Please invite a non-developer developer to the desk and have them (any of the genders) discuss why MATLAB is the greatest and most expensive language in existence. If you could present the pros and cons in a 1x1 matrix, that would be especially helpful.
The MATLAB language is public domain. The MATLAB program is proprietary. Programming languages can't be copyrighted or licensed, they are all 100% public domain.
@@techtutorvideos The language itself and its specifications is public domain, the name/branding is not. You can't copyright any form of language, including programming languages. Please just google it. There are even open source implementations of it and every other "proprietary" programming language.
Could you explain what he means by memory leaks happen but it will never be referenced again? As in does it keep on allocating more, or is everthing a const, regenerated upon altering?
@@nootnoot42 The Cult defines memory safety as the absence of undefined behaviours, such as data race, double free, dereferencing memory not/no longer allocated... A memory leak, a concept independent of Rust, is when you ask memory from the OS, but then forget about it without de-allocating it. One way to phrase that it is lost is that it's memory which won't be referenced again. As such, it is not unsafe per se. It keeps on allocating more. You can have leaks of constant size if there's not in a loop, but you cannot "alter" leaked data, that's the thing, the OS reserves it for you, and you no longer know where it is. Memory leak is a big deal when comparing memory models of different languages, and the absence of leak is a big selling point of garbage collecting over reference counting and manual management. What is funny about that is that the cult sounds like it's a non issue since it is not memory safety per se. The truth however, is that Rust is a huge upgrade from C/C++ when it come to avoiding leakage, since you can't cause them without using smart pointer or explicitly leaking potentially in combination with unsafe mode.
@@nootnoot42create a reference counting pointer a, create reference counting pointer b pointing to a, modify a to point to b: references will never reach zero so destructors will never be called and memory will never be freed, even if main completes. This behaviour is why .forget() is considered safe; rust memory safety does not guarantee no memory leakage (as proven by the first example). forget() takes ownership of a value and makes it impossible to re-reference, but does not call the destructor. An explicit leak.
That must have taken quite some prep work! So much of that feels like inside info that I am tempted to say the guy must have done at least some programming in Rust. Also, the blue wig matches the eyes so well 💙😆
It would be really nice if these videos would have references to all the tools and technologies being joked about. I would really like to learn about them
I would love to see an interview with a LaTeX enthusiast! I am sure that would be very entertaining since LaTeX is definitely much more efficient than all that MS Office nonsense.
I have written plenty of LaTeX, and lemme tell you - every time I have some incomprehensible error I can't find and need to go to stack exchange for the 12th time that hour, I despair that it's still infinitely better than MS Office for maths.
Please do one as a fresh computer science graduate who thinks the interview is actually for a job but realizes at the end that it was an unpaid internship
SUBSCRIBER 4 LIFE! - Oh my god dude!!! You got something here. You are a talented comedian that just so happens to know about tech. Make this a Niche Bro if you're into it. You got talent and thanks for the laughs.
Now that Lemmy is built in Rust and it's also caught in the middle on the Reddit Drama, I feel like it would provide a LOT of content for satire. I am sure your video is going to be as excellent as the rest!
You know, the "trust me" macro is a pretty accurate description of what using the unsafe keyword is. You're saying "okay rustc, lemme validate this part of the code for you". Instead of "unsafe", a more apt name could've been "assert_safety", or... "trust_me"
A premier that makes me wait for 2 weeks. Just as long as it takes to use "cargo build --release" to compile a rust hello world. You sure are taking the joke to the next level.
I laughed so hard at everything else he made fun of. This one hit too close to home, I smiled wryly at half of it, and winced at the other half. As always, superb job, though I think he's talented and funny enough that he can risk a bit more variation in the future.
I'm pretty sure it's the same for other videos tbh. The perl one felt especially on point with how it feels to encounter perl code anywhere in an open-source project.
I love rust, and I thought this was super hilarious. I died laughing at the trust_me macro, 'comeback after you learn haskell' or 'we didn't say it was a language for everybody, just for the elite'. I actually learned a bit of haskell/purescript a few years ago, so I know that haskellers respect rust and vice-versa (look at FPComplete). I can't wait for him to do one on mojo, once mojo hits a 1.0 release
"It's a little stricter with error handling. Essentially you're being tazered when you make an error. How else are you going to learn low level programming?" Fucking gold right here.
"Rust is an interesting mix of C++, OCamel, Haskel, DotA, Javascript..." "Javascript?" "I mean Lisp, Lisp" I feel attacked by all of this. How do you it so well?
"There are 5 games written in rust and 50 game engines" I am dying
me too its too true
I felt that one
that's so funny since only I have created more than 5 games in a pure Rust
Seems like I'm the only creator of those 5 games the author mentioned
Oh goodness, I can't stop laughing :D
The best quote. My honest advice for people serious about Rust game devoplement: Forget about the engine solutions. They are unfinished and untested in large scale commercial productions. You will hit a wall easier as the needs of your game grow compared to Unreal / Unity.
Instead, setup your own wgpu rendering and Rapier physics (if you need physics). There's nothing wrong in studying the engine solutions' specific parts such as bevy's skeletal animations, just keep the full control to yourself. It's more work and effort, but maybe if you are aiming for quick commercial game release, Rust is not the best language to develop with at the moment.
The unsafe macro being called trust_me had me dying
5 games and 50 engines had me dying.
Haha, yeah, I was gonna say “you can’t spell trust without Rust.”
I'm just picturing an unsafe macro called trust_me_bro throwing yeets
In Idris there is a function believe_me : a -> b
"I'm not here to tell you that Rust is the best language. You should've figured by now"
Fax 🦀
When I know nothing about a Programming language, I come to this channel to get a proper Introduction
bad idea !
Brilliant
Gotta say it piqued my interest about Rust and it confirmed my intuitions about C#
Actually really good take. If you learn the biggest pitfalls and struggles and think you can tolerate them, I don't think you're gonna mind the rest of the languages.
so accurate
Rust developers trying to rewrite their failing marriage in rust
everybody knows it's failing cause of this damn memory management xD
Why marry if you could just borrow instead?
They must be lacking tRust
I tried it but for some reason my gf is not very happy about using the borrowing model for our relationships.
yeet
"In Javascript you have to worry about memory because of Javascript" 🤣
That one got me too
Javascript - I love it!
@@blazehawkins2759 I wouldn't recommend it
@@Madar2252 why? wait lemme guess. Because you use RUST to write wasm? 😂
@@sudiproy4413 it's a reference from a video Interview with Senior JS Developer from this channel in case you didn't get the joke. Well, actually i wouldn't recommend it either
"In rust we are all geniuses" what a wonderful quote
…yet, they cannot handle a single pointer
A wonderful yet a big lie.
@@leshommesdupillyC devs obviously can’t handle them either considering rust exists in the first place
@@leshommesdupilly ?
@@uwuLegacy *the c devs that finally switch to rust
"So Iced is the best one?"
"It's the most complete one."
This is some of the most niche humor I've ever had the pleasure to be in on.
"And which part did you write in Rust? The frontend or the backend?" *visible confusion* "No the browser!" 😂
and the operating system
**Turns around in panic**
NO the browser!!!
Firefox goes brrr
This answer is goated 😂
Servo be like
"Throw all advantages from all languages, together. Now your code is unreadable. But it is safe."
That should be the slogan for Rust.
So true
Ah man that made me actually laugh haha
Let's be fair -- they avoided the messes of inheritance. Or ml modules. And they don't have higher kinded types (well, they have GATs which let you do the same thing).
@@einargs Why would higher-kinded types be bad?
"Who else needs to read this?" 🙂
I think that "Premieres in 10 days" is an allegory for how long rust build might take sometimes
_Very allegorical_
@@tanveerhasan2382 the sacred and the propane
Thredripper
Jeeez, is it just that unoptimized at the moment or what?
@@TheMohawkNinja llvm optimisation pipeline for release builds takes ages and then for incremental builds the long part is always gonna be the linking step (you can substitute a better linker depending on platform, e.g. mold for linux) because most linkers we have are archaic monstrosities that dont parallelise well and that doesnt play nice with the deluge of object files rustc will spit out for incremental builds
It's incredible to me how well you "get" the languages you parody. Like, it's clear you understand the inner culture and the most complex concepts of these languages.
ye, wouldn't be half as good if it were jus surface level jokes
He even got the hair right.
Yall clueless deluxe. We are not like this. The Rust language is winning anyway 🦀
"Is this the timer for the coffee?"
"No I just finished compiling" LMAO
Honestly facts. I sometimes see rust analyzer spend 2 minutes trying to compile the entire repo and itll sometimes shit on PROC MACRO NOT FOUND. ALSO L LOSER I DONT KNOW WHAT THIS "SeRdE SeRiaLize and DeSerIaLizE" IS. Re run it. Teehee, i made an ooosie, ur code is fine don'r hate me uwu
@@arizona_iced_out_boy Dont worry i spend 5 min compiling my java android application and spring boot services EACH
@@arizona_iced_out_boy the rust-analyzer compiles for a full hour compiling the substrate repo.
I don't get that meme, because if you use a powerful enough machine compile times in Rust are not a problem. Even if the crate takes longer than you want to compile, you can just split it into smaller crates.
Moreover, I have a project where both Rust and JS ecosystem is used, and producing a JS bundle takes like 10x more time than it takes to generate the WASM bundle part of it.
Meanwhile in Python, the time saved by not compiling is paid in runtime and bug hunts 😢
"now your code is unreadable, but its memory safe"
Tbf, wrap all of it in macros and it'll become more readable.
@@principleshipcoleoid8095 Someone at work actually does this.
A macro for checking error results
A macro for defining const values
etc...
I hate it.
@@principleshipcoleoid8095 now you have to also know what weird magic the macro does
@@khatdubellis it memory safe tho?
“I let my threads panic…for pleasure” 😂
"I have a macro for unsafe, it's called 'trust me'" 🤣 gets me every time
trust_me!
Dz XD
first what I had to do when tried Rust first time - is force unsafe because else multithreading communication with external hardware wont work
so funny xD
@@Morimea Yea? External hardware is inherently unsafe.
@@thegoldenatlas753 then what the point of Rust?
Entire modern programming is - communicating with multiple devices in multiple threads and sync data.
- And which part did you write in Rust? The frontend or the backend?
- "No the browser"
For those not getting the "write an operating system in three weeks" reference, Ken Thompson wrote the initial version of Unix in three weeks.
One week for the kernel.
One week for the file-system.
One week for the shell.
In assembly.
Could you share any resources regarding that? I wanna take a look how feasible that is even for a prototype
Not bad, but Terry Davis wrote one that could talk to God in 10 years.
@@ericconnor8419 Lol, this is perfect satire of any video comment section regarding Temple OS.
Ken and Dennis were fucking legends though
They don't make 'em like that anymore.
We need "Interview with UI/UX designer"
that would be interesting
Ligma
@@coldestbeer Ligma mama! got em!
Especially that one who constantly makes subtle changes in browser logotype.
Separate one with GNOME designer (I personally hate them and would be glad to see satire about GNOME approach).
those are two different people
and UX people are screeming at everything UI ""design"" people come up with
Damn, this wig for a Rust engineer already got me.
Complements his blue eyes nicely
@@gestaltengine6369 Facts it's the first thing I noticed and I like women
No programming gloves though
now i can't unsee it
why is he so attractive with it
@@heartache5742 Looks like Brad Pit with it. Crazy.
" after a well managed , well-mannered discussion , that will make everyone unhappy "
" im fully oxidized at this point "
incredible video , such great specific examples
We're on the same page that the "yeet" reference was about the "await" keyword discussion, right?
@@JMurph2015 Nah, it was about *another* flamewar about what we should call the keyword for early-returning inside try-blocks, IIRC. Eventually the lang team decided "You know what, fuck it, let's call it the "yeet" keyword until we have a working implementation, that'll stop the bikeshedding". So now "yeet 64" is a valid Rust statement in nightly.
"Lots of jobs for us, most are for startups to do some blockchain stuff.. and then go bankrupt" life is always on the razors edge when you are a Rust dev
"Disadvantages? Rust thinks you can't keep object lifetimes in your head" - brilliant!🤣
We've come full circle from "we need to see the compiler as the enemy" to "we need to see the compiler as our friend"
most languages compilers are your friend rust compiler is your frenemy
A good compiler is your friend and so is a good debugger
I love the idea of a Rust compiler that tasers you when you make a mistake. That will teach you quickly!
Ded in 3 minutes
It wouldn't be too difficult to adapt cargo-vibe to do this...
ua-cam.com/video/YvhlOtQAU0A/v-deo.html
@@blackmarvolo wheres the blteplug crate, but instead of sex toys you control a taser over bluetooth
"I am fully oxidized by now." Brilliant, thank you.
I am so hyped, i will sleep for the next 14 days straight.
😂😂😂
lol
This guy is secretly an immortal senior engineer who has seen it all and that's just his scream for help😂
Kill me, and I will Rust.
Tom is a genius
true.
lmaoooooo
JDSL ftw
He's a genius
Everyone send this to Prime until he watches it lol.
Petition to rewrite this interview in rust
To rewrite rust... in rust
@@flaksoft8003they already did that. The first version of the compiler was written in OCaml.
We need one of these for sys admins. With just the right amount of passive aggresiveness towards users.
+1
And active aggressivness towards devs. Lile kill -9 prod applications because of memory spikes
Dude, your videos are so good. Please do one for golang, and kubernetes!
golang devs have negative personality, though
I need a Kubernetes one! I have some PTSD from it.
so much down the rabbithole, we need a devops one, azure one etc.
The Kubernetes one would definitely kill me. I dream in YAML.
"I'm not here to tell you that Rust is the best language....... [silence]... you should have figured that out by now." 💘💘
True 🦀
9:45 of Rust love and not saying "Blazingly fast" once is a performance
rust is blazingly typed
I shit you not, my old software manager, when comparing Rust and C compilation times, told us that "C's compilation is blazingly fast". That phrase stuck with me and now I feel like he was making an inner joke while trashing Rust in some aspect.
@@PimpofChaosC is blazingly fast in segfaults and 0days LOL
Should’ve donned a fabulous moustache and a hoodie and a pair of AKG headphones for a complete package
Don't forget the swiss exercise ball.
... hey I have an AKG Headphone
@@blueberryiswar show me your homemade OS
I have seen this 3 time. It is so well done, very high effort. Great job! Their are so many extremely funny jokes and the delivery is executed so well.
It is one of his best videos. The Emacs one wasn't too funny!
"Not every dev learns Rust in a *lifetime* "
😅 For real, the funniest line, apart from I joined a couple of start ups in this month or I wanted to compile my personality into a crate... actually too many lool
Skill issue tbh
This is gold, every Rust developer should watch this as soon as they start thinking about learning Rust.
Existence of Rust developers who have not yet started thinking about learning Rust is a testament to the power of the Rust language and its compiler.
Theres like three youtubers I know that are criminally spreading their rust cultism.
@@ollicron7397I assume Mr No Boilerplate is a senior member?
Video needs to be deleted
"I'm currently rewriting the color blue in rust" had me literally burst out in laughter
The accent, the hair, the light, the words, everything is perfect.
Looking forward to Primeagen's reaction
The speed at which this became one of my favorite channels is unparalleled.
"I let my threads panic. For pleasure."
Found myself writing a lot of multithreaded Rust recently. I was ROFL for like 10 minutes after these lines.
Would be interesting ...
We need interview with a Labview developper too
is labview that popular
Among those who still remember it ...
"testing in rust is easier... because we're all geniuses"
I am still laughing 😂
It's not *not* true, though.
@@olivierfaure5896😂
"5 games and 50 game engines" so true (and i'm making one of them :)
literally everyone are either making game engine or GUI library in Rust
@@tui3264
To be fair, this is also true for all the programming languages, the number of games you have is usually half the the number of game engines people tried to make and failed hahahahaha
@@diadetediotedio6918 yeah it is easy to learn Graphics api by making game engine :p
@@tui3264 right, when we are too stupid to dig into an existing api some of us tend to do that.
@@diadetediotedio6918 I think its hard to build game engines in JS, so people only make games in it?
".. well mannered, well managed discussion which will make everyone equally unhappy " 🤣🤣
"There are currently five games written in Rust. There are also fifty game engines written in Rust" Oh maaaan, I feel seen lol
Fake news
5 games and 50 game engines - true, but making a game engine is so much more fun
That situtation is actually sensible and interesting. Graphics APIs (OpenGL, Vulkan, Direct3D,...) have the following challanges: 1) things are checked at runtime and *only* at runtime 2) exhaustive testing is impractical (you need the combinations of all physical GPUs and all drivers) 3) the API has a lot of variability (different implemented featuresets, different API versions,...). All in all, this is a hot mess for graphics & gamel developers. If some technology were to tame this (and prevent lots of grey hair for game developers), this would probably be worth billions and billions of dollars. Personally, I'm not sure that graphics APIs can be tamed with Rust without constraining the API functionality too much (there is just too much variety there...). TOTOH if these projects actually succeed, it would prove Rust to be a tool of truly monstrous powers...
@@sasas845 That's exactly the reason why wgpu exists, and it is beautiful.
@@sasas845 using Rust for game/gane engine development is painful.
@@marcossidoruk8033using any language for game or game engine development is always *eventually* painful, when you get big enough to actually run up against the hardware. Using Rust is making the assumption that the average to peak suckage will be lower than other languages.
You probably are thinking more about the scripting side, but you can host a runtime, including new Rust-flavored scripting languages if you want that hot loading experience.
@@marcossidoruk8033big skill issue
Waiting till July 1 is about like waiting till my Rust code finishes compiling.
Did it finish by now?
ETA tomorrow
@@UnabashedOops next life
Very funny nerds 🤓 as if Cpp does not compile as slow LOL
- Yeah, but nobody knows Haskell. We're all looking to learn Rust
- Come back after you've learned Haskell
coming to Rust from Haskell, I confirm that this really helps
Interview with an Ops Engineer (DB, Network, Infra etc) would be amazing
6:55 "No, I just finished compiling", had me dying 😂
I keep rewatching this throughout my Rust learning journey. Bravo 👏
This is just impossibly good! :-))
I have about 30 years experience with programming, I started when Pascal was still big, so I know a think or two about the languages.
So I tried Rust, picked just a simple hobby project (a curtain controller logic) and after two weeks I just couldn't finish it. Than I freaked out and returned to C++ and was done within a couple of evenings. Rust's learning curve is just... too much.
Although a bunch of ideas are interesting.
Please invite a non-developer developer to the desk and have them (any of the genders) discuss why MATLAB is the greatest and most expensive language in existence. If you could present the pros and cons in a 1x1 matrix, that would be especially helpful.
Shut up Hanque!
I have a coworker that unironically believes MATLAB is the best language
The MATLAB language is public domain. The MATLAB program is proprietary. Programming languages can't be copyrighted or licensed, they are all 100% public domain.
*proceeds to interview an enby*
@@techtutorvideos The language itself and its specifications is public domain, the name/branding is not. You can't copyright any form of language, including programming languages. Please just google it. There are even open source implementations of it and every other "proprietary" programming language.
Can’t wait for primeagen’s reaction !
“Is it time for the coffee?” - “No I just finished compiling.” LOL
He appears like a cool young version of Brad Pitt oxidized into coding Rust.
LOL, "Come back after you learn Haskell..normie." That is hilirious!
Ah yes! Famed automobile pioneer and systems programmer Harrison Ford.
lol
It sure takes a while to compile.
Because of the abstractions
You think cpp is faster? hahaha
“There are currently 5 games written in rust, and 50 engines.” 😂
As a Rust fanatic, this is hilarious, on point af.
Could you explain what he means by memory leaks happen but it will never be referenced again? As in does it keep on allocating more, or is everthing a const, regenerated upon altering?
@@nootnoot42 The Cult defines memory safety as the absence of undefined behaviours, such as data race, double free, dereferencing memory not/no longer allocated...
A memory leak, a concept independent of Rust, is when you ask memory from the OS, but then forget about it without de-allocating it. One way to phrase that it is lost is that it's memory which won't be referenced again. As such, it is not unsafe per se. It keeps on allocating more. You can have leaks of constant size if there's not in a loop, but you cannot "alter" leaked data, that's the thing, the OS reserves it for you, and you no longer know where it is.
Memory leak is a big deal when comparing memory models of different languages, and the absence of leak is a big selling point of garbage collecting over reference counting and manual management. What is funny about that is that the cult sounds like it's a non issue since it is not memory safety per se. The truth however, is that Rust is a huge upgrade from C/C++ when it come to avoiding leakage, since you can't cause them without using smart pointer or explicitly leaking potentially in combination with unsafe mode.
@@nootnoot42create a reference counting pointer a, create reference counting pointer b pointing to a, modify a to point to b: references will never reach zero so destructors will never be called and memory will never be freed, even if main completes.
This behaviour is why .forget() is considered safe; rust memory safety does not guarantee no memory leakage (as proven by the first example). forget() takes ownership of a value and makes it impossible to re-reference, but does not call the destructor. An explicit leak.
@@thomson765 Thank you
Not a real fanatic! Video needs to be removed!!
That must have taken quite some prep work! So much of that feels like inside info that I am tempted to say the guy must have done at least some programming in Rust. Also, the blue wig matches the eyes so well 💙😆
went for the Rust Dev look, but ended up with the Gorillaz lead singer look
Took it as a brithday gift. Thanks!
It's worth the wait
"When I see a C++ dev, all I see is a future Rust dev." Holy crap, I don't remember agreeing to be in this interview.
He mentioned gluon at the end. I didn't know about it. Looks amazing actually.
It would be really nice if these videos would have references to all the tools and technologies being joked about. I would really like to learn about them
LET'S FUCKING GOOOOOOO🎉🎉🎉
I would love to see an interview with a LaTeX enthusiast! I am sure that would be very entertaining since LaTeX is definitely much more efficient than all that MS Office nonsense.
I have written plenty of LaTeX, and lemme tell you - every time I have some incomprehensible error I can't find and need to go to stack exchange for the 12th time that hour, I despair that it's still infinitely better than MS Office for maths.
Please do one as a fresh computer science graduate who thinks the interview is actually for a job but realizes at the end that it was an unpaid internship
Love how he looks tired like evey other rust developer.
it's because he's stoned
2:48 - "There are currently 5 games written in rust, and 50 game engines" HAHAHAHA
Solid! Missing the split keyboard tho 😅
this was amazing. Please make one for Haskell/Scala/Functional programmers
There's a lot of Haskell mentions in his emacs video - worth checking out
"In JavaScript you worry about JavaScript" thats why its the best
"...worst" here FTFY
"The compiler is your friend" - I see someone has been watching No Boilerplate
8:03 Cult... community, community 🤣
SUBSCRIBER 4 LIFE! - Oh my god dude!!! You got something here. You are a talented comedian that just so happens to know about tech. Make this a Niche Bro if you're into it. You got talent and thanks for the laughs.
I honestly cannot wait for the Prime react to this one!
I'm watching this now and then I'll watch the 36min version Netflix Prime will make.
Option
Beautiful 🦀
"we compile the entire company at runtime"
This is one of the best videos, on par with the senior JS dev
I feel like I bought into an ICO. Waiting for it to compile.
OOF. This hit hard as a Rust dev, who also worked for a blockchain company that died lol.
Your own fault! Take the --> L
"We do not talk about Java here" I'm dying lol
Now that Lemmy is built in Rust and it's also caught in the middle on the Reddit Drama, I feel like it would provide a LOT of content for satire.
I am sure your video is going to be as excellent as the rest!
2 more days! Just in time for sprint planning lets go!
You know, the "trust me" macro is a pretty accurate description of what using the unsafe keyword is. You're saying "okay rustc, lemme validate this part of the code for you". Instead of "unsafe", a more apt name could've been "assert_safety", or... "trust_me"
I've seen this in my queue as premiering soon for so long that I've wondered if that was the joke...
fifteen days? are you serious
Yeah, what? Who puts videos on for premiere 15 days in advance?
@@vesk4000 - I hope he changes it to 30 days now.
@@vesk4000rust developers
It is part of the Joke
That's how long it takes to `cargo build --release`
It should have been called "Junior Rust Dev". There's no such thing as a senior rust dev.
A premier that makes me wait for 2 weeks. Just as long as it takes to use "cargo build --release" to compile a rust hello world.
You sure are taking the joke to the next level.
I laughed so hard at everything else he made fun of. This one hit too close to home, I smiled wryly at half of it, and winced at the other half. As always, superb job, though I think he's talented and funny enough that he can risk a bit more variation in the future.
I'm pretty sure it's the same for other videos tbh. The perl one felt especially on point with how it feels to encounter perl code anywhere in an open-source project.
@@Soitisisit Yeah, I kind of figured that it was just my turn. :)
I love rust, and I thought this was super hilarious. I died laughing at the trust_me macro, 'comeback after you learn haskell' or 'we didn't say it was a language for everybody, just for the elite'. I actually learned a bit of haskell/purescript a few years ago, so I know that haskellers respect rust and vice-versa (look at FPComplete). I can't wait for him to do one on mojo, once mojo hits a 1.0 release
I cnrged so hard at everything. Not funny.
"It's a little stricter with error handling. Essentially you're being tazered when you make an error. How else are you going to learn low level programming?" Fucking gold right here.
"Rust is an interesting mix of C++, OCamel, Haskel, DotA, Javascript..."
"Javascript?"
"I mean Lisp, Lisp"
I feel attacked by all of this. How do you it so well?