7 ms·
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 civ
by lars_francke 3y ago
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 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-1682519944 https://github.com/serde-rs/serde/issues/2538#issuecomment-1...
This is so sad.
- monocasa 3y agoYeah, just like 'people don't leave jobs, they leave managers', 'developers don't fork source, they fork maintainers' feels equally true.
- Ygg2 3y agoTo quote a funny YouTuber: Rust community doesn't report bugs, we complain about in GitHub issues for two years until project owner quits.
- simonw 3y ago> It's all the right of the author. And he's done so before. What do you mean by "he's done so before"?
- lars_francke 3y agoLocked 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.
- lars_francke 3y agoI 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.
- __jem 3y ago> 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.
- shkkmo 3y ago> 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.