3 ms·

> This has already been discussed extensively elsewhere. I am not sympathetic to concerns over useing a trait. Rust is not the language for you if you don't lik

> This has already been discussed extensively elsewhere. I am not sympathetic to concerns over useing a trait. Rust is not the language for you if you don't like traits. Feel free to collect a full refund on your way out. Without weighing in on the merits of the comment, the delivery feels very Poettering-esque.

JohnFen 3y ago
I know it's not entirely fair, but seeing stuff like this makes me wary of the Rust community.
- cmrdporcupine 3y ago
  Yeah, it's not fair because there's no way this person represents the Rust "language community" it's just a couple people arguing on a bug ticket. And in fact there's others who would make a counter argument that excessive reliance on traits is a bad over-complexity-smell. The reality is it's fairly large language community already, and lots of people have lots of different opinions.
- seanhunter 3y ago
  Every language will have people who make extreme statements of one kind or another. I wouldn't call that representative of the community in general.
- littlestymaar 3y ago
  I have bad news for you about <any language> community… People behaving poorly on github issues/PR discussion is so common in every language it tells much more about the internet/open source culture than it tells about Rust users (there's no such thing as a “Rust community” nowadays BTW, it's not 2016 anymore and the language user base has grown so much the user base is now as fragmented as it is for any mainstream language).
dathinab 3y ago
yes and it has little to do with liking or dislinking traits tbh. having to import a trait to use what boils down to a single pure function is never good design BUT the convenience methods defaulting to "standard" base64 instead of "url safe" base64 because it's one of the things where people don't think about there being more then one standard/configuration and it then loading to bugs in their code so deprecating it makes sense, and without a braking change (which makes no sense here) you can't replace it with anything better and because of the prelude module the import isn't that bad e.g.: `use base64::prelude::{Engine as _, BASE64_STANDARD};` and even ignoring that most imports are auto generated, sorted and formatted by rust analyzer for most people most of the time so it's eitherway at most a minor anoyence so I can understand that the author is feed up with people annoying him about that again and again and again
frodowtf 3y ago
Pretty sure the maintainer is also a Discord mod.

JohnFen 3y ago

I know it's not entirely fair, but seeing stuff like this makes me wary of the Rust community.

cmrdporcupine 3y ago
Yeah, it's not fair because there's no way this person represents the Rust "language community" it's just a couple people arguing on a bug ticket. And in fact there's others who would make a counter argument that excessive reliance on traits is a bad over-complexity-smell. The reality is it's fairly large language community already, and lots of people have lots of different opinions.
seanhunter 3y ago
Every language will have people who make extreme statements of one kind or another. I wouldn't call that representative of the community in general.
littlestymaar 3y ago
I have bad news for you about <any language> community… People behaving poorly on github issues/PR discussion is so common in every language it tells much more about the internet/open source culture than it tells about Rust users (there's no such thing as a “Rust community” nowadays BTW, it's not 2016 anymore and the language user base has grown so much the user base is now as fragmented as it is for any mainstream language).

dathinab 3y ago

yes and it has little to do with liking or dislinking traits tbh. having to import a trait to use what boils down to a single pure function is never good design BUT the convenience methods defaulting to "standard" base64 instead of "url safe" base64 because it's one of the things where people don't think about there being more then one standard/configuration and it then loading to bugs in their code so deprecating it makes sense, and without a braking change (which makes no sense here) you can't replace it with anything better and because of the prelude module the import isn't that bad e.g.: `use base64::prelude::{Engine as _, BASE64_STANDARD};` and even ignoring that most imports are auto generated, sorted and formatted by rust analyzer for most people most of the time so it's eitherway at most a minor anoyence so I can understand that the author is feed up with people annoying him about that again and again and again

frodowtf 3y ago

Pretty sure the maintainer is also a Discord mod.