I heard a PeerTuber I follow talk about controversy around “Rust” as a dangerous cult or something, but that she thinks people should put aside their “petty grievances” and focus more on what good the project will do for Linux. I’m out of the loop, but I think Rust is a programming language, right? Anyone know what this whole thing about a cult is? I want to be filled in on it, because it seems important.
The remark about style warnings is really alien to me. Style warnings are something I’m accustomed to when programming in nearly any language. I can’t remember the last time I used a language where whatever IDE I happened to be using didn’t have style warnings. And I’ve never had trouble adapting. “Oh right, C# convention is PascalCase methods. Oh, Java is camelCase”. In fact I’ve been jumping between a C# project and a Java project recently, and I haven’t been finding it difficult. Rustc having some linter-type warnings built in is a bit novel I guess, but really not a fundamentally different experience. It’s really not any more difficult to disable those warnings for a Rust project than for a C# project. I don’t think I can understand calling that “not okay”.
There’s a difference between “adding a style checker yourself” (or the project owners doing it, if it’s not your project) and “having a style checker built into the core tools that yells at you unless you either conform, or turn it off in every single project you write”.
Sure, C# convention for the standard APIs and whatnot may be PascalCase, Java camelCase, and whatever. But that doesn’t mean that Everyone Must Follow The Standard Convention. That way lies Python and frankly, Python’s “there is One Correct Way to do everything” culture really turns me off.
But even Python doesn’t do this. Neither does Java. Yeah your IDE might, but that’s a weird IDE feature then. And we can just use a different IDE. You can’t just a) use a different compiler and b) tell everyone who’s interested in your project to use the different compiler or ignore the warnings, they’re spurious trust me bro.
You can disable specific warnings as a project setting, not just with rustc/cargo but with every build toolchain I’ve used in the last ~10 years. It’s very common for me to find a project with at least one specific warning disabled. That really isn’t a “trust me bro” – people can look at the project, see which warnings are disabled, and decide for themselves if that is reasonable.
You CAN disable it as a project setting, but then you have to put that in as boilerplate in every single project you write for the rest of time, while the “just conform” people don’t.
Like, Rust’s style checker nonsense is “remind me later” culture. Trying to wear you down by making you say “no, stop trying to get me to use your style instead of mine” in every. single. project until you break down and stop caring.
That’s why it’s not okay.
(inb4 “but what about other warnings!”: those are actual problems with the code, or stuff that might turn into problems. “Having a different coding style than the language authors’ personal decree” just isn’t.)