Gergely Orosz

For more details about this conference, head to leaddev.com.

If you'll be at either of them, I'll see you there.

And with this, let's get back to Rust and to Alice.

I wanted to ask why Rust is getting so popular, but I think we're starting to answer this question, right?

Why is it a good or a bad thing to have a garbage collector?

Java has a garbage collector.

C Sharp has a garbage collector.

The performance overhead, the fact that you will not be able to control the memory as much.

For someone who has not yet seen Rust code, how would you describe it, how it compares to, for example, TypeScript?

So it's pretty easy to read, even if you know some similar languages, you can look at it and you can get a rough idea.

Rust has a learning curve on the side of the more difficult languages to learn.

What do you see devs typically struggle with who are new to Rust?

And what are the things that just makes it click for them?

Yeah, a direct async graph.

I can see how that's frustrating.

Rust has another model that might be new for, especially for people coming from language types, is Rust's ownership model.

What is the ownership model?

And how does reference counting relate to all of this?

And on Rust also is another thing that was new to me, the borrow checker.

Yes, because now it has been, as soon as you change it, it went out of scope.