3 ms·
> This is a thread about Rust and people hijacked it with Go comparison, saying server are better suited for Go, etc. Umm, no, they didn't. This thread started
by burntsushi 12y ago
> This is a thread about Rust and people hijacked it with Go comparison, saying server are better suited for Go, etc.
Umm, no, they didn't. This thread started with someone whining about Go's type system.
> I wouldn't trust anyone that has dabbled in Java/Go/.Net and made various servers/web-applications to look upon schematics of a real-time nuclear power plant controller, let alone be in same room with the code.
How deliciously condescending of you!
And I guess, C++ people are somehow more competent for this particular task of working on nuclear power plants?
Count me skeptical.
- Ygg2 12y ago> Umm, no, they didn't. This thread started with someone whining about Go's type system. I meant the entirety of this discussion, see the name of thread - Is Rust web yet? Not really. > How deliciously condescending of you! > And I guess, C++ people are somehow more competent for this particular task of working on nuclear power plants? Yes, yes it is. I didn't say that anything about C++. I'd assume that whatever C / Ada / Assembly /Machine code variant people working on critical embedded software use. C++ has exceptions, that alone disqualifies as critical performance language.
- burntsushi 12y agoI respectfully submit that you missed my point. I randomly picked C++ as a language you didn't mention. My point is that you were being condescending. I'll be more direct: please don't be condescending. (I really don't know how to deal with the fact that you're seriously talking about who is and who isn't qualified to work on nuclear operations based on languages they've used.)
- Ygg2 12y agoAnd you missed my point. Right tool for the right job. You don't take a fork to drink a soup and you don't take a spoon to cut meat (unless the knife is duller than the spoon). Sure sometimes is fun to improvise by using knife as a fork, but that's a silly way to eat. With that in mind a different language operates with a different set of limitations and a different mental model of execution. Most people that program in Java don't have to worry too much about memory footprint, whether GC pause will kill performance, etc. Fact that they are using GC means they accepted non-deterministic pauses as part of the programming. To move from that frame of mind to a really performance sensitive where frequency and voltage matters requires a radical shift of thought.
- burntsushi 12y ago> And you missed my point. Right tool for the right job. You didn't say, "Don't use Go for nuclear operations." You said, "I don't want people who've ever used Go to work on nuclear operations." The former is perfectly reasonable. The latter is a gross over generalization and extremely condescending. > Most people that program in Java don't have to worry too much about memory footprint Here's a novel thought: not every programmer who uses Java has only used Java.
- Ygg2 12y ago> You said, "I don't want people who've ever used Go to work on nuclear operations." Artistic license/ Rule of Funny. Using a correct form, wouldn't have been as funny. Also yeah, it's supposed to be condescending. I was mocking the author, mirroring his condescension towards the Rust team (to paraphrase said - stop checkmarking GC, get crackin' on Rust; Wouldn't use Rust in a nuclear power plant).
- burntsushi 12y agoGot it. You insult large groups of people for comedic effect. Uh huh.
- Ygg2 12y agoYup. Just like personZ.