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.
Rust Lang
Rules [Developing]
Observe our code of conduct
- Strive to treat others with respect, patience, kindness, and empathy.
- We observe the Rust Project Code of Conduct.
- Submissions must be on-topic
- Posts must reference Rust or relate to things using Rust. For content that does not, use a text post to explain its relevance.
- Post titles should include useful context.
- For Rust questions, use the stickied Q&A thread. [TBD]
- Arts-and-crafts posts are permitted on weekends.
- No meta posts; message the mods instead.
Constructive criticism only
- Criticism is encouraged, though it must be constructive, useful and actionable.
- If criticizing a project on GitHub, you may not link directly to the project’s issue tracker. Please create a read-only mirror and link that instead.
- Keep things in perspective
- A programming language is rarely worth getting worked up over.
- No zealotry or fanaticism.
- Be charitable in intent. Err on the side of giving others the benefit of the doubt.
No endless relitigation
- Avoid re-treading topics that have been long-settled or utterly exhausted.
- Avoid bikeshedding.
- This is not an official Rust forum, and cannot fulfill feature requests. Use the official venues for that.
No low-effort content
- Showing off your new projects is fine
No memes or image macros
- Please find other communities to post memes
No NSFW Content
- There are many other NSFW communities, let’s keep this related to the language
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.
That particular interaction was handled poorly, but isn't this issue about adding essentially two 3 line helper functions to the library? Forking just for that seems unnecessary. You can instead make a new library that depends on this one and which defines your helper functions, or just copy the helpers into each project you use. It would be more convenient in base64
, but it's not like it's the end of the world either.
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.
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...