4 ms·
> Person B doesn’t understand why, so asks why 30 minutes and not 4 hours? Person A thinks Person B is judging them for their personal preferences, and says tha
by bscphil 4y ago
> Person B doesn’t understand why, so asks why 30 minutes and not 4 hours? Person A thinks Person B is judging them for their personal preferences, and says that they chose 30 minutes because they like it. Person B then deduces that Person A is an idiot who thinks that the systemd default behavior should be determined Person A’s personal preferences.
My experience is that something like 25% percent of the people who run open source projects are just "like this" and there's nothing you can do about it. If you end up forced to deal with them because there aren't other contributors who can step in, or because they're the BDFL of the project, your best bet is just to move on and/or fork it to do what you need. I have probably half a dozen soft forks I maintain myself because the project leads are impossible to work with for exactly this reason.
This isn't about open source explicitly, to be clear. It's just more obvious and visible when it's happening because there's often 1:1 contact on bug trackers. Likewise, it obviously doesn't excuse shitty entitled behavior from issue reporters, of which there is plenty. I'm only making a comment about what I've observed from developers.
- lokar 4y agoThis is mostly why I don’t bother trying to fix things is open source projects. IME, people are dramatically less professional (meaning communicating clearly, considering input, etc) then I see at work. The exceptions tend to be projects mostly run by people doing it as their day job for a big company.
- unconed 4y agoIt's a problem where they stare themselves blind on what the ideal rule or code or mechanism should be, not realizing the requirement is something entirely different like "a user should never lose their data". These people have no idea how to build products and have never read anything on the subject.