That is an experience I do not want on my phone and computer.
Instead, a total absence of control. If something borks up you’re just hosed. Possibly no way to do a thing in the first place, to later get borked.
As I’ve told many defenders of Apple’s downright criminal restrictions - Android works the same way, if you don’t fuck with it. My first phone? Absolutely I ran custom ROMs and installed whatever from wherever. My current phone is stock. Most people’s are.
The ability to fuck with things is crucial. Actually fucking with things is optional.
Days since last issue for me on Apple products: 15 years – I started Apple product pairing about 15 years ago with the iPhone 3G and the unibody aluminum MacBook a little earlier, and I don’t have memory of them doing me wrong.
Compare that to my servers: Days since last issue: 1 0 day – I started using Linux close to 25 years ago, starting with RedHat Linux 6 where GNOME was the big hot new thing. While I wouldn’t consider myself an expert, a relatively benign system update shouldn’t have botched the system for me the way it had yesterday. This was not the first time, and it will not be the last time… and how do I know it won’t be the last? My other server, hosted in the cloud by Oracle in the San Jose region lost power, went offline for several hours; the block storage attached to the VM did not get unmounted properly, which in turn did not get remounted properly, so when the system came back, it couldn’t get everything back up and running automatically, and required some manual intervention before I can get back on my Lemmy instance.
For whatever reason, this just seems to be par for the course on anything that’s not locked down. Yet, the scary boogieman of “if it something borks you’re hosed” seems to be the norm. Track record kind of speaks for itself here, at least for me, this model works. I’m more than happy with the security and stability on things that I use to keep the lights on.
PS: Also getting fond memories of deploying Deep Freeze on Windows 3.11 Workstations so users cannot mess it up. Before doing that, going through to re-image problematic machines was a daily job, after locking everything down so the systems cannot be messed with? Monthly, just so we can deploy updates. Recurring theme much?
Instead, a total absence of control. If something borks up you’re just hosed. Possibly no way to do a thing in the first place, to later get borked.
As I’ve told many defenders of Apple’s downright criminal restrictions - Android works the same way, if you don’t fuck with it. My first phone? Absolutely I ran custom ROMs and installed whatever from wherever. My current phone is stock. Most people’s are.
The ability to fuck with things is crucial. Actually fucking with things is optional.
Days since last issue for me on Apple products: 15 years – I started Apple product pairing about 15 years ago with the iPhone 3G and the unibody aluminum MacBook a little earlier, and I don’t have memory of them doing me wrong.
Compare that to my servers: Days since last issue:
10 day – I started using Linux close to 25 years ago, starting with RedHat Linux 6 where GNOME was the big hot new thing. While I wouldn’t consider myself an expert, a relatively benign system update shouldn’t have botched the system for me the way it had yesterday. This was not the first time, and it will not be the last time… and how do I know it won’t be the last? My other server, hosted in the cloud by Oracle in the San Jose region lost power, went offline for several hours; the block storage attached to the VM did not get unmounted properly, which in turn did not get remounted properly, so when the system came back, it couldn’t get everything back up and running automatically, and required some manual intervention before I can get back on my Lemmy instance.For whatever reason, this just seems to be par for the course on anything that’s not locked down. Yet, the scary boogieman of “if it something borks you’re hosed” seems to be the norm. Track record kind of speaks for itself here, at least for me, this model works. I’m more than happy with the security and stability on things that I use to keep the lights on.
PS: Also getting fond memories of deploying Deep Freeze on Windows 3.11 Workstations so users cannot mess it up. Before doing that, going through to re-image problematic machines was a daily job, after locking everything down so the systems cannot be messed with? Monthly, just so we can deploy updates. Recurring theme much?