|
|
|
|
|
by imoverclocked
1428 days ago
|
|
Yes, let’s choose something that will work with everything, say: RS232 for any wired data connectivity
110 VAC for any kind of power
802.11b for any kind of wireless data connectivity
… Now that we have these mandated, let’s zoom to the present day and figure out just how bad of an idea each of those decisions were. I don’t know what “mandating interoperability” would mean for all cases in the original argument. eg: Does someone need to write software that can run on every single operating system that supports Bluetooth to perform a firmware update for AirPods before releasing them? That sounds pretty abysmal for anyone that doesn’t have the resources to understand/target/maintain a process for BeOS/Haiku/Linux/Android/iOS/Windows/whatever my car’s console is running/etc. OTOH, you could write a standard for firmware updates to devices over different channels and see who would adopt it. Make sure it is future proof and covers all currently known use-cases. If it’s adopted by enough people, you aren’t using your local government to write something in stone which will likely be outdated in a decade or so anyway. |
|