Live data from Hacker News

A Sad Day for Rust

words.steveklabnik.com

481–490 of 1001 posts

Re: A Sad Day for Rust

#481
post #305

Earlier quoted context omitted.

If I understand correctly, your anecdotal evidence is what makes this not "armchair psychology"?

What's wrong with simply sharing personal observations based on the decades of related personal experience? Anyone who has some training in science has learned to always be looking for patterns.

Nothing. I simply don't value this kind of loaded and facile analysis very much.

Re: A Sad Day for Rust

#482
Elm packages are not allowed to use JavaScript, period. I personally thought this very restrictive and unnecessary. But after seeing this, maybe Elm/Evan is doing it right after all.

Re: A Sad Day for Rust

#483

Earlier quoted context omitted.

Here is an example of an actual comment. I believe the thread is deleted now: > "seriously? Please just stop writing Rust. You do not respect semver, you do not respect soundness, so why are you using a language predominantly based around doing these things right?" This is what I was thinking of when I wrote "far, far over the line."

That comment is demeaning, unhelpful, and in very bad taste. It's the comment that the delete functionality on GitHub was made for. However, one of the other participants in the thread immediately called out this comment. So you have a constructive dialog, a single bad actor, and said single actor being called out by the people having the constructive dialog. That doesn't sound like an unhealthy community to me, to b…

I agree that the comment is in bad taste but what I don't see this being considered a "far, far, far over the line." comment when I take into consideration that it had been posted in reply to the maintainer's also dismissive comment "this patch is boring" so, yes, the user has definitely been rude, but chances are it's a visceral response too.

Otherwise if that event is far far over the line I wonder what out of the blue insults or death threats qualify as.

Re: A Sad Day for Rust

#484
post #118

Earlier quoted context omitted.

Yeah, I agree. “It’s all reddit’s fault” is not helpful at all and simply wrong from reading that thread.

You cannot get the full context from a single reddit thread; as I mentioned in the post, this situation is the product of multiple events. You'd at least need the posts from all of them, let alone that this is only one of the posts from this situation on reddit in the last day.

I mean this in the most respectful way possible, but have you considered your own antagonism against Reddit is not healthy for the community? Throughout the years I've seen you talk down about Reddit and the people there quite a bit. I get that they're "rougher" than the ideal Rust citizen but they're also real people and members of the community. It's probably best not to judge one of the largest sites on the internet if for no other reason than it breeds hostility.

Re: A Sad Day for Rust

#485
post #385

Earlier quoted context omitted.

You can't squat and redirect subreddits to external sites. I have personally been granted mod of a subreddit that had been redirecting to another website. Its against the rules and the subreddit will be banned at which point anyone can use /r/redditrequest to take it over. Even if that did work however, people would create adjacent subreddits that would end up to be defacto sureddit, for example /r/competitiveoverwat…

I’ll defer to you on this, but I definitely know I’ve come across subs where this has been happening for years and they’re not shut down.

Its completely possible that nobody has reported those subreddits to the admins.

Re: A Sad Day for Rust

#487

Earlier quoted context omitted.

Counter: what about the tension and potential community split when a fork starts getting popular? I was there (as a user who closely followed development) during the nodejs > io.js split. While it worked out in the end, it felt like a bitter battle at first. Node survived by chance perhaps. We have our async-std vs Tokio right now, I'd imagine having another split (at least in opinions and preference) on actix would…

nodejs io.js split was a great evolutionary step. It allowed for the chaffs to fall through making node a stronger project because it was clear that neither of the sides was going to "win" outright. If the argument is that "maintainer is not doing his/her job of being a maintainer" and this argument is accepted by the users, then should the project be forked by someone who will do his or her job of being a maintainer…

The risk was worth it, node was stuck (in 0.12), and it was the whole thing, not "one of the things that you use to run JS on the server". A fork of actix wouldn't enjoy the same conditions that existed with Node.

Does the fork care as much about TechEmpkwer benchmarks? What happens if it is slower because it forbids unsafe even where it makes sense?

There was a looming cliff in Async/await, which caused a split to some extent (some old libraries that no longer have maintainers, changes that make updates difficult). A fork with those changes looming would mean divergence when rewriting to support Async/await.

Maybe I'm being too cautious, but I doubt we'd have had a successful fork earlier. Let's see if it happens now ...

Re: A Sad Day for Rust

#488

A lot of this thread has it wrong, and this wrongness contributes to the problem which led to this. I have two simple mantras which establish my philosophy here: 1. YOU are responsible for your dependencies. 2. Open source participants are volunteers and owe you nothing. It was never Nikolay's job to vet actix-web for you, nor did it become his job when the library became popular, nor does invoking "security" change…

Given that Chromium is a open source project, and lost of people here are strongly against Google's proposal to limit the ability of ad block extensions, with much stronger words compared to this incident. What's your opinion on that?

Re: A Sad Day for Rust

#489

Earlier quoted context omitted.

Then why open source at all if there is not some interest in helping others who have "aligned interests"?

So that others can pick the pieces they need, if they care to. It's an offer to the world, not a sales pitch.

If you post random code on the internet at your leisure, sure. When you have a marketing campaign for your open source tool... then yea, it's a sales pitch.

Re: A Sad Day for Rust

#490
post #4

It brings up the question — as a developer, how can you best set boundaries on your customers so that you can have some degree of control over the toxicity of the culture that you're exposed to when interacting with them?

It brings up the question — as a developer, how can you best set boundaries on your customers so that you can have some degree of control over the toxicity of the culture that you're exposed to when interacting with them? Personally, I don't think you really can. I think the best thing to do from a developer/maintainer perspective is to identify toxic communities and do you're best to ignore them entirely. That's pro…

No idea why this is being down-voted--it's a great answer. You can't make people act civilly, but you can shun them and vote with your feet.

Life is too short to deal with shitty people.

Post reply on HN