Thread with 7 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 i think that attitude might come from the fact that newcomers often recoil at discovering this language is significantly different from ones they're familiar with, and saying something like โ€œno really, this thing is good, please spend a while longer with it, you'll get it eventuallyโ€ is important for them. but then this mantra gets repeated also at people who've gotten enough experience to really see where things fail. the eternally troublesome context problem

Open thread at this post
mcc , @mcc@mastodon.social
(open profile)

@hikari In my case, one thing that helped me get over that same hump without having to develop cult behaviors was I had spent time around compilers and taken basic steps toward writing my own compiler, so for a number of the early "wtf?" moments in Rust a compiler person went "consider how much easier this makes to write the compiler, and how much harder the compiler would be without it" and I immediately went oh no. oh no. oh noooo I see it now you'll never be able to fix this one :(

Open remote post (opens in a new window)