4 ms·
> Only see comments doing that are on here. Reddit comments went into tinfoil hat territory. Discord comments went into calling for dtolnay's head.
by Ygg2 3y ago
> Only see comments doing that are on here.
Reddit comments went into tinfoil hat territory.
Discord comments went into calling for dtolnay's head.
- shkkmo 3y agoRight, but the original characterization was clearly about the discussion on the github issue that was closed.
- Ygg2 3y agoEven 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 https://imgur.com/a/ei6wzxW
- slikrick 3y agoyou 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
- Ygg2 3y agoI 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.
- shkkmo 3y agoAre 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 https://github.com/serde-rs/serde/issues/2538 I already referenced the worst comment and it falls closer to brutally honest than actually rude.
- Ygg2 3y ago> 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-1684896969 https://github.com/serde-rs/serde/issues/2538#issuecomment-1... https://archive.is/bHQS6#issuecomment-1684896969 https://archive.is/bHQS6#issuecomment-1684896969 - https://github.com/serde-rs/serde/issues/2538#issuecomment-1682639314 https://github.com/serde-rs/serde/issues/2538#issuecomment-1... https://archive.is/bHQS6#issuecomment-1682639314 https://archive.is/bHQS6#issuecomment-1682639314 - https://github.com/serde-rs/serde/issues/2538#issuecomment-1684609445 https://github.com/serde-rs/serde/issues/2538#issuecomment-1... https://archive.is/bHQS6#issuecomment-1684609445 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.
- workingjubilee 3y agoMy 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.