Thread with 9 posts

jump to expanded post
mcc , @mcc@mastodon.social
(open profile)

@hikari The "if Rust does it a certain way, it must be right" attitude is infuriating and never more so than when you're actually trying to write Rust. It leads to really shallow thinking about the language.

What's really weird is I've stumbled into interacting with the actual Rust core devs and/or inventors a few times and they're all really nice, humble people who *don't act like this*. You ask about an odd decision & they either talk about complex tradeoffs or are like "oh that was an error"

Open remote post (opens in a new window)
mcc , @mcc@mastodon.social
(open profile)

@hikari Like, I want to be writing Rust, but there are a lot of things in it that come down to "this is a bad thing that was situationally necessary in order to achieve some other goal" and you want to figure out ways to cope with the bad thing and someone's coming along trying to convince you that the bad thing is Good Actually and it's just exhausting and unhelpful.

The only positive thing I can say on this front is I've also interacted with the Go community and they're even worse about this.

Open remote post (opens in a new window)
kulupu jyn , @jyn@tech.lgbt
(open profile)

@hikari @whitequark @mcc i want to write a blog post about this at some point, there's no way to ensure work gets done other than blocking stabilization, so stuff either ends up unstable for years or just never implemented because it looks like too much work github.com/rust-lang/rust/pull

also the rust culture is one of burnout, whole teams are burned out, and so the RFC process is where ideas go to die and you can't get anything done without knowing people personally and spending absurd amounts of time pushing for it yourself

Open remote post (opens in a new window)