3 ms·
Naah, in my observation it is kind of bashing which is almost always around the fact that Go is not Rust, which amazes me each time why certain individuals do t
by kunley 3y ago
Naah, in my observation it is kind of bashing which is almost always around the fact that Go is not Rust, which amazes me each time why certain individuals do that instead of simply coding in Rust or writing more about Rust.
(Funny that it applies almost exclusively to Rust folks; I never saw any negativity towards Go from Zig folks, for example).
These individuals will of course downvote this comment as well as my previous comment, because they are so deeply emotionally tied to their choice of language that they hate even mentioning the mechanism; but I don't care about my points here, instead I care much more about the truth and honesty
- rami3l 3y agoRust dev here. I really love the fact that most of the time people from the Golang community would like to say "look what I've made with Golang!" That's the sign of success: the users (here I mean general devs) should not care too much about the language per se, they still have applications to ship! Rustaceans tend to talk more about cool new language features. They are critical to what Rust does, but maybe they have also got too much attention.
- eloisant 3y ago> Go is not Rust, which amazes me each time why certain individuals do that instead of simply coding in Rust or writing more about Rust. As I said: typically those devs want to use Rust but their team or employer decided to go with Go instead. So they keep writing Go wishing they were writing Rust instead (and maybe secretly hoping to convince their colleagues and bosses to switch to Rust). So it happens precisely because Go is popular and get selected for those projects.
- erik_seaberg 3y agoThis. I’m interested in Rust for safety, but I really just want to be allowed to use a language aimed at empowering experts rather than novices.