Видео

Absolutely fantastic format! Priceless for Rust newbies. Thanks, Tim! ❤

Yes this is what a tutorial should be like so beginners can understand what they are doing. Amazing work🙏

I really hope this happens! I've always wanted to visit NZ, and go to a Rust conference, and I'm totally onboard with merging the two!

how that is even possible

i had a short time worked with her, she is so brilliant

You should have made it clear that this is a teaser for a full interview. I happened to expect it so i checked the description. Make it easier to find the full vid

from c++😢 to rust❤ long live rust🎩👑

I am learning rust! Its so good! Keep it up!

Heya Tim AccelerantGPT referred me to your channel, i must say ts amazing!!! Time to get rusty:)

I have no idea what that guy talked about 🙂

I think that no video is near to the brown university book explanation. It's hard way of learning. But it's also nice to do some variation in the learning style.

Hi Tim, Trying to get a Rust on AWS Workshop written. Aimed at helping people of all levels get started writing rust and using the Rust sdk for AWS. No need to twist my arm to come to NZ and visit my sister as well.

1- Saw him using Helix as the text editor 2- Instantly liked the video and subscribed to the channel. pretty based 🗿

Thank you so much for the video! I didn't know you had a YT channel. I just picked up your book, Rust in Action! Thanks so much for all your teaching!

Thank you for doing this, Zeeshan has a very interesting and impressive career.

Another thing I found: The subtext seems to be out of sync. At the start it's okay. After 7:30 the text is some seconds faster than the sound

Nice Interview. Thank you. But there seems to be some problem with varying loudness. I get the impression the interviewee doesn't sit tight or something of that kind... ?

Zeeshan, I wish to see you as well apart from listening you after long time. Anyway good to listen you

Thank for doing this Tim! I hope to see more system programming contents like this.

so it starts with Shed? Registered!

Cool! Any idea on the ticket price yet?

lol - personal sounds good, im in!

That's an awesome idea. It has been way too long since my last NZ trip, and I have 12 months to come up with a talk.

Great idea.

great video would love to see more of this, trying to understand how to read a rust codebase without getting bogged down or reading things line by line tediously is hard for newbies

my friend also learned rust, but then became homeless, so I have different opinion about Sust

@9:37 Just curious, would chars() be safer (in case of weird UTF-8 characters), and work just as well as bytes() ?

Thanks Mr Clicks! - This would be a good candidate for a "part 2" - with async/tokio maybe? 👍

Great video! Thanks Tim

can you make a single video of each tips? or put timestamps instead? your content is helpful. thank you so much for sharing..

Ive been watching Rust content for so long that my mind went to Copy just before you wrote Oof(), when I code in Rust, this knowledge just goes somewhere else in my brain and is unaccessible.

how do you find most contracts? (assuming you have had more than 1 for this time period).

Interesting vid (as usual😊), but the forced subtitles, please nooooooooo!

Nice insights and so glad to see you making what looks like a great living focusing on what you are passionate about.

Are you Kevin Powells brother?

I guess having a secondary income like from book sales helps on the financial side.

Berkeley Mono is truly an elite font

I think you could’ve also just done a convolution and had the kernel that averages all the values in the kernel window.

Didn’t finish the whole video yet, but you’re supposed to store the MEAN not the average… Edit: My bad, I read "mean" and my brain understood it as "median". Sorry about that.

The notion that other languages don’t have lifetimes for their variables is obviously false. It’s erroneous code to return references to stack variables, leak memory by stealing from a smart pointer and not doing free/delete yourself, or dereference an iterator whose underlying container has been destroyed.

good point

Hey Tim, big fan.

Very generic and vague answers. Use less resources, faster, more secure, good for uptime... In what ways, and compared to what exactly?

promo sm 😥

Any 2024 update of your book planned?

Here's the raw data for you to play with: gist.github.com/timClicks/54a5eb46ff633bfc15d403c0c9984e8b/

What about get-all-npm-packages 😂

Can you upload the list of this deny/forbid usage to github gist please?

I highly recommend everyone to read about `core::iter::successors`. It's so simple, yet extremely flexible!

No matter the resolution I choose, the video is at 14fps 🧐