[tucnak]

> Is the borrow checker a pain in the ass? Yeah. But is it necessary?

You've missed the primary point of the post entirely. Borrow checker per se is not the problem; it's the sheer amount of everything. There's multiple ideas of perfection. Those of us to have very much enjoyed ostensibly imperfect Rust of 2018 find this particular, current flavour unappealing. It may as well be capable tool in deft hand, however, as-is the case with everything in life, you cannot help but ask yourself THE question; is it worth my effort? For me personally, if I were looking for better C/C++ in 2025, I would choose Zig before Rust any day of the week (one exception being Postgres stuff, pgrx ecosystem that is really special!)

But then again, anything beats writing C for a living.

[worik]

> But then again, anything beats writing C for a living.

I love that.

My happiest professional programming has been C

I guess diversity of taste is a wonderful thing?

[uecker]

Yes, I also love writing C.

[tucnak]

Guilty pleasures :3

[khuey]

> Those of us to have very much enjoyed ostensibly imperfect Rust of 2018 find this particular, current flavour unappealing.

I believe everything in this post (except `cargo -Zscript`) was in the Rust of 2018.

[metaltyphoon]

Traits, generics, ownership, RAII shows up in many languages, so what other concept outside of lifetimes does Rust introduces?

[ridiculous_fish]

Affine types, variance, higher-rank trait bounds, phantom data, MaybeUninit, and the whole macro and proc-macro systems are some examples of concepts that I found to be challenging when learning Rust.

Dyn-safety is another but I had encountered that previously in Swift.