Thanks for the kind words! Yeah, my short Git videos got popular. I've always been a Java dev at heart, but I see Mojo really changing the game. More content to come!

I'm working on it! So much more to cover! I'm looking forward to full native Windows support from Mojo myself!

Darcy? You mean the @Scrumtuous one?

Thanks for the kind words! Lots has changed since I uploaded this. I need to make a new one! The ownership model is one of the biggest changes I need to get used to as a Java dev. Maybe you could help me out with that on the next video?

​@@cameronmcnz i can give you a little rundown of ownership/borrowing. it's how memory is managed in rust. essentially each value has a variable that's called it's owner. there can only be one owner at a time and when that variable goes out of scope, memory is freed automatically. when you assign a value to one variable and then to another, the ownership is moved to the new variable. functions work similarly in that when you pass a value to a function, memory is freed. one important aspect though is that it's only freed when you actually take ownership. if you only borrow the value, the memory isn't freed, because you don't own value. i'll touch on borrowing a bit below, but conceptually this model is kind of a combination of garbage collection and manual memory management, but with the performance benefits of manual memory management. now i'll get into borrowing a little bit. there is a difference between borrowing an immutable value and borrowing a mutable value. when you borrow an immutable value, you're only allowed to read from it by default. you can't modify the value until you've given it a reference using the & syntax. so basically by using a reference, you're borrowing the immutable value. when you have a mutable value, you have to reference with the &mut syntax. there can only be one mutable reference to a piece of data in a specific scope, which hypothetically prevents data races because no other references to the data can exist at the same time in the same scope. i recommend reading "the rust book" which is their official online book/tutorial because i've skipped over some important details that would make this comment too long. there's only so much i can put in a comment but this is more of a basic rundown of some of the core concepts.

​@@cameronmcnz i can give you a little rundown of ownership/borrowing. it's how memory is managed in rust. essentially each value has a variable that's called it's owner. there can only be one owner at a time and when that variable goes out of scope, memory is freed automatically. when you assign a value to one variable and then to another, the ownership is moved to the new variable. functions work similarly in that when you pass a value to a function, memory is freed. one important aspect though is that it's only freed when you actually take ownership. if you only borrow the value, the memory isn't freed, because you don't own value. i'll touch on borrowing a bit below, but conceptually this model is kind of a combination of garbage collection and manual memory management, but with the performance benefits of manual memory management. now i'll get into borrowing a little bit. there is a difference between borrowing an immutable value and borrowing a mutable value. when you borrow an immutable value, you're only allowed to read from it by default. you can't modify the value until you've given it a reference using the & syntax. so basically by using a reference, you're borrowing the immutable value. when you have a mutable value, you have to reference with the &mut syntax. there can only be one mutable reference to a piece of data in a specific scope, which hypothetically prevents data races because no other references to the data can exist at the same time in the same scope. i recommend reading "the rust book" which is their official online book/tutorial. i've skipped over some important details and there's a lot more information that you should know before making a video that would be too long for a comment.

@@cameronmcnz do you have a discord server or something? i've tried to comment but i think it's being marked as spam because it's so long.

@@crab-cake I keep intending to set one up with the team but haven't yet. I guess we probably should given the videos telling everyone about it. I'd love it if you were the first to join!

The good old Mojo PythonObject! It's an interesting resource that can go back and forth between Mojo and Python worlds. Video to come!

Imma be honest with you man. I'm building a team of Mojo enthusiasts and everything is happening so fast that we haven't yet set up the server. That was 'forward thinking' but I haven't set that up yet. Let me get someone on the team to do that this week.

no worries. we are all enthusiasts in MOJO be cause it's too new and too young but also too promising. keep up.@@cameronmcnz