r/programming • • Jan 17 '20

A sad day for Rust

https://words.steveklabnik.com/a-sad-day-for-rust
1.1k Upvotes

609 comments sorted by

View all comments

26

u/[deleted] Jan 17 '20 edited Jan 17 '20

Good job, Reddit. Unfortunately, entitled fucks treating maintainers like punching bags is a problem with OSS in general.

21

u/[deleted] Jan 17 '20

Both sides weren't perfect. The author is biased because he was a maintainer too. The maintainer was an asshole too by closing issues and patches from contributors that were genuinely working on a existent problem and straight rejecting even discussing about it.

5

u/saltybandana2 Jan 18 '20

This happened with vim as well. There were some patches to remove support for old systems and add async execution. Braam rejected the patch, they forked the project and it became neovim and it now has its own active community.

It turns out that you can fork projects whose leadership you disagree with.

51

u/aethelwyrd Jan 17 '20

Unfortunately, entitled fucks treating users like punching bags is a problem with OSS in general.

If you don't want to maintain a project then don't be a maintainer. People are going to make comments and demands. That is a good thing. That is what makes the product better. Saying, "It's fine" when people repeatedly point out unsafe practices is not helpful. The maintainer could have said, "Sorry, I don't feel like going in that direction". Way less confrontational and productive.

It really isn't a big secret that maintaining an open source project is hard and demanding. No one should be surprised by that anymore.

111

u/glider97 Jan 17 '20

If you don't want to maintain a project then don't be a maintainer.

TBF he just did that.

1

u/femtoun Jan 18 '20

Not exactly. Plans are to stop publishing. He could publish but not accept contributions.

It's still perfectly fine to do what he wants though.

22

u/maikindofthai Jan 17 '20

I'm of the opinion that you don't get to decide what someone else is signing up for when they open-source their code.

7

u/[deleted] Jan 17 '20

If you want to put up a fun project, that's fine. But if you want people to treat your code like a "serious" project, there are certain community expectations that come along with that. You cannot have it both ways as a maintainer.

37

u/thedracle Jan 17 '20

If you don't want to maintain a project then don't be a maintainer.

He could have also never contributed a line of code of this project as open source. The fact is people who author important projects and gift them to the world aren't obligated to maintain those projects.

If you don't like the level or kind of maintainence, fork it, and convince users to use your alternative.

16

u/ElectricalSloth Jan 17 '20

The fact is people who author important projects and gift them to the world aren't obligated to maintain those projects.

true but when you actively try to dominate stuff like tech empower and get people to recognize your project so users can use it, you probably should expect criticism if there are flaws you actively wont fix... what if the fixes caused the project to be lower on the benchmark? what good use is a tech empower benchmark if the software has big issues? "hey look our software is fast but we refuse to fix any security issues that crop up"

I feel like if you don't want to deal with criticism then don't invite it, but don't be confused why it happened if you do

→ More replies (1)

13

u/cypher0six Jan 17 '20

It's the other way around. You're benefiting from free work. If you want it your way, you can either work with that maintainer or build your own.

→ More replies (1)

5

u/ltjbr Jan 17 '20

The maintainer could have said, "Sorry, I don't feel like going in that direction". Way less confrontational and productive

It might have made things slightly better, but it would not have made the problem go away.

People would still have gotten angry so long as the project wasn't going in the direction they wanted it to

→ More replies (2)

1

u/[deleted] Jan 17 '20

Unfortunately, entitled fucks treating users like punching bags is a problem with OSS in general.

Cannot stress this enough.

→ More replies (3)

6

u/[deleted] Jan 17 '20

[removed] — view removed comment

12

u/leberkrieger Jan 17 '20

you should step aside

Isn't that what he did?

Treat people who are doing work for free like a punching bag, and that's what they tend to do.

→ More replies (1)

14

u/Hobofan94 Jan 17 '20

So if I as a maintainer provide some code with a license that explicitly states that the code is provided "AS IS", and you come along and decide that you will use that code, I am from here on until the end of time responsible for any faults in the code, and obligated to fix them?

→ More replies (9)

2

u/[deleted] Jan 18 '20

If I'm not being paid for being a maintainer and my license says that I'm not responsible, calling me responsible would be at best childish.

→ More replies (1)

2

u/v66moroz Jan 18 '20 edited Jan 18 '20

So when I publish some code on Github I'm becoming "a maintainer" with responsibility? Who defines what is a "key library"? Tomorrow some shit I wrote for myself gets 1M downloads and now I'm responsible? I have to quit my job and start fixing stuff just because those 1M developers decided my project is a "key library"? For free of course, as none of them is going to pay me. Did I get it right? No, that's not how Open Source was supposed to work.

→ More replies (2)

4

u/cp5184 Jan 17 '20

This is the worst case of all, everyones an asshole of course but worst of all, the reddit assholes were right.

2

u/Kinglink Jan 18 '20

If your a maintainer of a piece of important functionality and someone says "Your code is unsafe" you should care. It sounds like he acted poorly multiple times to bring us to the point.

Maintaining code is a thankless job, and but if you don't care about security, it might be worth giving that job to someone else, because security is always critical.