Comment by ChuckMcM
2 days ago
I know it feels like a semantic quibble. Consider that you can boot and run Linux on the processor that powers a Seagate hard drive. You can even run a c compiler and develop new code on it. But when you pull one from its protective wrapping after you bought it from a distributor, it isn't a "computer", it's a storage device (dedicated function, aka an appliance for storing data), that you can plug into a general purpose computer, or into a smart television, or into a DVR, Etc.
Similarly, for a long time, the CPU in my washing machine (a Z80) was the same processor that my first computer with disk drives had (a Cromemco System 3, aka a "business computer" which ran CP/M) but it was intentionally hobbled to just run the display, run some timed processes, and read various sensors.
Building "purpose built systems" that happen to have a computer processor inside of them because it is cheaper or more efficient to implement their functions in code, are what pretty much everyone considers "appliances." Sometimes obviously so, as in washing machines, and sometimes not so obviously when you can buy "apps", or "personality modules", or "game cartridges" for them to make them do something useful given the constraints of the fixed I/O they have.
But if you have a computer system that is intentionally hobbled to a fixed set of things, then for me, it's an appliance and certainly not a general purpose computer.
You make a good point, I guess the issue is not manufacturers considering it an appliance or even users considering it an appliance. My main issue is with them intentionally locking it down from the user. For example, in the washing machine I see no reason for it to have a locked bootloader with no way for the owner of the device to unlock it. If some Yahoo wants to hack their washing machine and run Doom and Linux, I don't see why that should matter to Samsung or Whirlpool or Google or Apple or whoever.
So I guess my issue is not thinking of these general purpose computers as appliances, so much as it is treating the owner of the device as a security threat. Secure by default is good, as the vast, vast majority of users would not be tinkering with stuff. But if they want to (and that can fully void warranties IMHO), and they own the device, I don't think the manufacturers should be blocking them.
> So I guess my issue is not thinking of these general purpose computers as appliances, so much as it is treating the owner of the device as a security threat.
And in this we are 100% in agreement.
The issue in the US is that liability falls on the manufacturer if they don't "reasonably prevent" the device from deviating from its designed function. So if you hack your washer machine to do a 20,000 RPM spin cycle and it fails catastrophically and kills someone, they have some liability there. Parents have successfully sued when their kids have 'modified' things that later killed or injured that kid. Just as burglars have successfully sued for being injured while breaking into a facility. THAT part of US tort law is really broken and needs to change.