> You are as empowered to fix this as anybody else, if it presents a real problem for you.
I’m getting sick and tired of this argument. It’s very user unfriendly
Do you work in software? If yes, do you own a component? Have you tried using this argument with your colleagues that have no idea about your component?
Of course they theoretically are empowered to fix the bug, but that doesn’t make it easier. They may have no idea about how filesystem internal. Or they may be just users and have no programming background at all
It's not unfriendly, it's just how it is. The fact you're comparing it to industry shows you don't get it.
Open source doesn't work for you. You can't demand that it do things you want: you have to push and justify them yourself, and hopefully you find other people along the way who want the same things and can help you.
I taught myself to program as a teenager trying to fix bugs in Linux. If I could do it, anybody can. That's what makes it empowering.
Well I think you're completely right, in a way. But I also don't see the problem with people telling other people to not use the software or to complain about it. They are totally in their right to complain about stuff. Now obviously if the complaining involves requiring people to work for some feature you want, that's entitled and wack. Same goes for throwing a fit because maintainers went for systemd instead of your own favorite init system.
But being open source doesn't mean people shouldn't or can't just say "this is bad" or "don't use x" or even "this X feature doesn't work when using Y" (now If what they are saying isn't true, sure we should call them out)
It's normal and in fact I think it should be encouraged, as not everyone can be aware of potential problems they could have with a piece of OSS that is already known in some obscure dev mailing list. The more people are informed and aware of potential issues, the less they will be surprised and complain about it when they start using it.
(Fwiw I love btrfs, and I think it's very reliable)
I’m getting sick and tired of this argument. It’s very user unfriendly
Do you work in software? If yes, do you own a component? Have you tried using this argument with your colleagues that have no idea about your component?
Of course they theoretically are empowered to fix the bug, but that doesn’t make it easier. They may have no idea about how filesystem internal. Or they may be just users and have no programming background at all