To be clear, there is nothing wrong in using proprietary tools or licenses; I do, too. (The reason I use Tux as my mascot is not because I'm a Linux zealot, it is because I happen to like the whimsy involved, and have chosen to use Tux as a (non-exclusive) "brand" of sorts for myself. For example, I created and use a (plymouth) bootsplash animation of Tux rotating its eyes in opposite directions on my Linux machines. Drop me a PM if you want the debian package.
)
The problems arise when someone ideologically opposed to libre licensing interfaces with libre communities. It causes useless friction for all involved.
The worst case scenario is when libre software is mixed with non-libre software in the same project or recommended workflow. The libre users have issues with the non-libre components, and the users coming from the non-libre, vendor-supported side get frustrated with the perceived hostility of the libre side (because the users do not realize they are not paying customers anymore, just
participants, and dislike the loss of customer privileges like having the moral grounds for demanding features and fixes). It just makes a mess where nobody is happy.
I'm a
Help Helper at heart, and just want users to have tools that make them efficient and powerful, and not waste resources and time doing their tasks. I know and understand the benefits of proprietary/vendor products, and the benefits of libre products. The two aren't exclusive, but when mixed in a workflow, one
must understand and accept
both to be able to make it work well; and the Raspberry Pi foundation clearly does not. Which annoys me, because it causes useless and unnecessary friction in the communities I participate in.