JFC. When will open source projects like @rustlang learn that putting toxic people like this in positions of ANY authority is unacceptable. https://github.com/marshallpierce/rust-base64/issues/213 . He’s showing you who he is, and you’re not listening.
How is the Rust team responsible for some random GitHub dude having a strong opinion? Literally anyone can make a repo on GitHub and be a jerk.
I’m confused. What makes you think they have been put in a position of authority? Anyone can simply create a fork, or a separate project completely, and go a different direction. You’re not obligated to use any third party crate.
I do agree that they handled that interaction pretty poorly, though.
JFC. When will people learn that there will be toxic people in ANY community of sufficient size.
Also, as far as I know this crate isn’t official in any capacity. Not to mention that base64 isn’t terribly complicated if you don’t like this crate (https://en.m.wikipedia.org/wiki/Base64)
This post just sounds like trolling.
… Why are you digging up random drama from nearly a year ago?
Also, this guy isn’t affiliated with the Rust team AFAIK. And even if he was, this is his crate, not
rustc- he can do whatever he wants with it, and you can fork it if you disagree.Edit:
> Account created 11 months ago
> This is its only interaction
Seems legit.
I want to learn Rust so I can better enjoy the drama surrounding it.
@canis_majoris I *wanted* to learn rust, but I’m all set for toxic communities, so …
Maybe I’ll just stick with charming snakes.
Your post is more toxic than the one you linked to.
I was thinking the same thing when I was trying to use the new base64 code instead of the deprecated version: it’s unnecessarily complicated. I remember thinking “why is this so hard, so convoluted?”.
Any good forks yet? Open-source is great at solving problems when you can move on from assholes…
simple-base64. It works the way you’d expect:
use simple_base64 as base64; ... let decoded = base64::decode("YmFzZTY0")?;
