Comment by tolerance

The main benefit that I see it of having the source code to the software running on the devices you own is that you can always fix or modify it if and when you want to. Lots of things can happen such as the law changing, the company going out of business, the company stopping support for your device, or you just wanting to make some changes to how it works to better suit your lifestyle.

This doesn't mean that everyone will dive right in and make the code changes by themselves, but it does allow for paying someone knowledgeable to come in and make the changes for you. The same kind of way that you can (or used to be able to) get someone knowledgeable in cars to come in to fix or change things for you.

Think of it as having access to the device's schematics so that you (or someone knowledgable) can make repairs to the device when you need to.

This brings me to another point, that in addition to having the source code for the device available, there way to build and deploy the code to the device also has to be made available, otherwise it's only a shadow of a solution.

"Within reason" is doing a lot of lifting in that sentence, isn't it? What I define as reasonable FOSS solutions, many executives would not agree with, but that doesn't mean they're not practical or acheivable.

Your Snake example also doesn't seem very fair - there are many large, concentrated FOSS movements and organizations that are doing good. More and more - albeit very slowly and sporadically - there are governments and organizations choosing to invest in self-hosted FOSS solutions. And you focus on hackers expressing curiosity doing silly but interesting things on various types of systems. Come on.