My comment was referring to the impression that people who like Rust seem to think that you either also accept Rust as the best thing ever, or you don’t get it. I probably shouldn’t have mentioned it, because now the thread will be about Rust.
My comment was referring to the impression that people who like Rust seem to think that you either also accept Rust as the best thing ever, or you don’t get it. I probably shouldn’t have mentioned it, because now the thread will be about Rust.
I don't think Rust is in any way unique in having people who think that way...
An anecdote: I recently opened a position on my team, and got two applicants on the same day who ignored the project description, and basically said we should hire them to tell us how everything we do could be better if we rewrote multiple projects in Rust.
Of course it's completely possible for a programming language to be both (A) really well-designed and (B) have annoying people among its community. I suspect that's the case here.
It's not the case of the rust dev team, which seems very balanced. But I've met a few rust enthusiasts that match the worst of the fancy FP or Typing fan boys.
The thing I hate about rust is abbreviated keywords like “fn” and “mut” because it sounds like fricken mutt. A function is a function not a fn, and is it really so hard to type “mutable”?
There’s more important things in life to worry about than rewriting codebases in language Z.
Edit: Fat arrow?
I don't read code in English, even though I'm a native speaker. So its kindof a silly question: this would only come up when walking someone else through the code. I internally read code using data-flow and control-flow graphs. The written abbreviation is just shorthand for a specific type of graph vertex (or edge).
[1] https://doc.rust-lang.org/book/ch18-01-all-the-places-for-pa...
There is Func<T> - that's a delegate type.
things.Select(thing => thing.Stuff);
I verbalise the brackets as "thing goes to thing dot stuff".I love Rust, but I think it does go over the top, more so than other languages.
Also, give it a few years and the loud and annoying people will have moved on to being loud and annoying about something else.
So it goes.
It is more a C replacement
To the extent that you should have exceptions in your software, Rust's panic picks that slack up pretty well, and to the extent you should have error handling C++ exceptions were a bad idea and sum types like Result are much better.
Note that although Rust's types don't have inheritance the traits they can implement do. Which is much more likely to be something you actually wanted than say, C++ multiple inheritance.
https://www.stroustrup.com/quotes.html#:~:text=%22There%20ar....