Hacker News Reader

Hacker News

Comment by lars_francke | Hacker News Reader

Full thread

lars_francke

The issue has now been locked and no further conversation can take place on it. This is without a further comment.

I found the discussion to be mostly very civilized and focused on finding solutions for those affected.

https://github.com/serde-rs/serde/issues/2538

It's all the right of the author. And he's done so before.

Unfortunately, I'm afraid this could lead to a more fragmented ecosystem which is a pity.

It takes a long time to build trust but it can be destroyed quickly. I'm not sure if the author cares about that though. From my reading of the comments he doesn't.

"If there is implementation work needed in some build tools to accommodate it, someone should feel free to do that work (as I have done for Buck and Bazel, which are tools I use and contribute significantly to) or publish your own fork of the source code under a different name."

https://github.com/serde-rs/serde/issues/2538#issuecomment-1...

This is so sad.

View on HN

> I found the discussion to be mostly very civilized and focused on finding solutions for those affected.

I really disagree with this characterization of the discussion. While there's plenty of more or less dispassionate comments focused on finding a solution, there's a greater number of people from the peanut gallery drowning that out with comments that amount to "I don't like this!" at best and questioning the integrity of dtonlay at worst. I feel like this demonstrates some of the worst features of open source software on github, where a bunch of nobodies feel the need to add their totally useless input rather than participating in good faith to find solutions and make the software better. You even see comments like that here, speculating that dtonlay is trying to break cargo and force people to use bazel, which is just an insanely conspiratorial and bad faith speculative interpretation that is obviously untrue and helps no one.

> While there's plenty of more or less dispassionate comments focused on finding a solution, there's a greater number of people from the peanut gallery drowning that out with comments that amount to "I don't like this!" at best and questioning the integrity of dtonlay at worst.

Only see comments doing that are on here.

The comments on the github issue are all pretty productive and constructive. The worst is the commentator that calls the approach 'despicable', but also provides constructive feedback and helps describe the problem.

> Only see comments doing that are on here.

Reddit comments went into tinfoil hat territory.

Discord comments went into calling for dtolnay's head.

Right, but the original characterization was clearly about the discussion on the github issue that was closed.

Even if it was civil it was going to annoy the hell out of maintainer due to sheer number of notificiations. I was by accident in Chrome WEI commit, simply horrible number of notifications.

Also I'm not lying about (albeit hyperbolic) calls for dtolnay's head. From one of Rust Discords.

https://imgur.com/a/ei6wzxW

you just still don't make sense in your replies to users. literally no one asked about discord or reddit, this conversation is about the GitHub discussion.

don't move goalposts

I didn't move the goalpost - it's how I interpreted the peanut gallery part.

But ok, let's say limiting yourself only to GitHub comments, you can still find doubt casting and uncharitable interpretations:

> Nice micro-optimization. And if you bury your head deep enough into the sand, doesn't sacrifice anything important either.

> "The only supported way ..." is a polite way of saying "Works for me, WONTFIX".

> Another interpretation of an earlier comment is that he is all-in on bazel/buck and does not care about cargo. Both interpretations have me concerned.

> And ~80 comments with "This doesn't work for me".

Even in this case, the __jem comments make sense. Many people are just writing their version, "I don't like this, " meaning any interesting message is drowned out by noise. THAT will make any maintainer limit to contributors.

Are you just making stuff up? Not one of those quotes are comments are on the github issue that was closed and which was being discussed in this thread: https://github.com/serde-rs/serde/issues/2538

I already referenced the worst comment and it falls closer to brutally honest than actually rude.

> Are you just making stuff up? Not one of those quotes are comments are on the github issue

It's customary to assume other side is arguing in good faith and not making stuff up. I assumed you read all the comments, had access to Github, so you wouldn't have problems finding them. But apparently that wasn't the case.

- https://github.com/serde-rs/serde/issues/2538#issuecomment-1... https://archive.is/bHQS6#issuecomment-1684896969

- https://github.com/serde-rs/serde/issues/2538#issuecomment-1... https://archive.is/bHQS6#issuecomment-1682639314

- https://github.com/serde-rs/serde/issues/2538#issuecomment-1... https://archive.is/bHQS6#issuecomment-1684609445

> I already referenced the worst comment and it falls closer to brutally honest than actually rude.

It's hard to take this at face value when you mistook my quotes for outright fabrication. You either didn't read them all, or you convienently forgot the examples I cited.

Also nice micro-optimization comments is dishonest, apparently dtolnay felt the optimizations provided for his use case were strong enough to warrant a fix.

My remark was an observation based on the obvious public resentment, rather than necessarily an exhortation to do so. I promise you, I will not be so cagey and ambiguous when I actually call for someone's head on the chopping block.

Yeah, just like 'people don't leave jobs, they leave managers', 'developers don't fork source, they fork maintainers' feels equally true.

To quote a funny YouTuber: Rust community doesn't report bugs, we complain about in GitHub issues for two years until project owner quits.

> It's all the right of the author. And he's done so before.

What do you mean by "he's done so before"?

Locked issues with a comment similar to "works for me"

I'm not complaining. It's his project, it's his right. He will be overwhelmed by notifications and this is probably the only way he can stay on top of things.

I don't have to like it either though.

I should expand: This happened to me twice where there was still discussion between people to find solutions for them. In both cases the majority of people accepted the answer of the maintainer but it was still unhelpful for them and they were discussing workarounds.

This discussion was cut short by just locking the issues.

The second time it happened to me I stopped our sponsorhip out of frustration. That also sucks and is a bit petty. I acknowledge that.

Reply on news.ycombinator.com