Re: Open Standards and Open Source
Except we do, in fact, have tons of audio codecs and, as long as you use an open one, what actually happens in the real world is the software looks at what it is and picks the right decoder to play the file. People who work on compression can make a new one, like when Opus was created, with almost no visible effect on users except the benefits of better audio quality and smaller file sizes. If we decided that we needed to mandate that audio formats needed to be interoperable, then you could only make minor patches and we'd still be stuck with the first allowed ones, which were much less efficient than what we count on today.
Standards in software define what you can do. A radio standard defines what kind of data you get on the signal, and when you want to transmit pictures as well as audio, you need a new method. Most of the time, the benefits of standards are so obvious that people use them without being forced. I use HTTP to exchange data, not because someone told me that's the only allowed way to send API requests, but because it's easy for many things to use it. If I felt like it, I could implement a different protocol atop TCP and standardize only on that, or I could use only IP and do my own stream control, or I could eschew IP and build my own routing system. If I had a reason to think I could do those things better, then maybe I would.
There are a few cases where mandating a standard makes sense. Your radio example is a good one, but not because of user annoyance. It is a good one because the radio spectrum is a common resource which should be managed for the public benefit, not monopolized by any particular user. What I oppose in many cases is not standards, which are great, but mandated standards which makes it very hard to change anything no matter how better the new version might be. I especially oppose this when the environment makes it really easy to choose between standards. Mandating a standard on the phone network made sense because there's only one network, so it needs to work for everyone. I have a feeling that would have happened anyway because it's less work that way, but fine, mandate it. On the internet, it's easy to have as many different communication apps as you can fit on a phone, and they can have different purposes. You can have encrypted ones, ones that do file transfer, ones that are entirely decentralized, ones that are anonymous, ones with mesh networks, and if I don't like the idea of one, then I just don't use it. If they all have to be interoperable, then I either get none of that because you can't plug an anonymous mesh network app into one run by Facebook and expect them to understand one another, or I have to take all the features together even if I'd prefer not to.