Read on Twitter
Working at an IT company means you can work on the concept and iterate without ever showing it to the users. You only get feedback from users once you release, and it's filtered by customer support.
In open source we get feedback during design, iteration and after the release.
In open source we get feedback during design, iteration and after the release.
When you build things, you need to decide what use cases to support and what not to cover. You can't do it all.
Now imagine people commenting and bringing up 1000 edge cases that will never happen, but they really wish you cover. Or ask you to reconsider covering their use case.
Now imagine people commenting and bringing up 1000 edge cases that will never happen, but they really wish you cover. Or ask you to reconsider covering their use case.
That's why a lot of open source ends up with feature bloat which hurts maintenance. Open source tend to say yes, or else these users will take it to forums/Twitter/Reddit to haunt you how you don't care about X, Y or Z.
Emily summarizes it beautifully: https://twitter.com/EmilyKager/status/1321603336051789824
Emily summarizes it beautifully: https://twitter.com/EmilyKager/status/1321603336051789824
The good news is that at Home Assistant we're great at saying no. Sadly that also means that harassment of our devs happen. We've added things in place to make sure to protect them: code of conduct + rules about what we aim to support, even if it makes a vocal minority angry.
In the end, if you try to do all, you end up achieving nothing.
