4 ms·

Adobe Creative Cloud is the Tyler Durden of software.

TheOtherHobbes 11y ago
Actually it's the Windows 10 of software. Which is the problem: if you hire a builder or a plumber and they do something stupid which causes you significant harm, you can sue them. And you'll probably win. If you buy a car and it's defective and causes you significant harm, you'll likely get compensation from a class action suit. How did destructive software errors get an exemption from the legal principle of accountability? (I know the EULAs say whatever, but that doesn't mean they can't be challenged in court.) Adobe, MS, Apple and the rest don't need to care about software quality because they don't need to worry about expensive legal action by customers. Stupid crap like this will continue to happen until that changes.
- Nutmog 11y ago
  I think it's fair to put the blame for data loss on users as long as it isn't done maliciously. That's because users are the ones in the best position to protect against it by making backups in proportion to how valuable their data is. It would be a nightmare if Adobe had to make a backup of every customer's computer just in case their software had a bug that deleted something. Much more efficient for the user to just have a single backup protecting them from bugs in all their software rather than all their software redundantly doing it.
- AsyncAwait 11y ago
  I agree that some stronger regulation may be needed, but applying a broad "punish for a bug" strategy will have terrible effects for our industry as it will lead to a stagnation in innovation and a reluctancy to experiment. (We can already see this with the "Error 53" bug, where Apple is actually doing the right thing by not letting the secure enclave be compromised and getting sued for it). Look, bugs in software are as old as software itself, comparing software to a builder is not helpful because it is simply not the same thing at all - software is a lot more abstract and the effects of doing certain things are far less measurable at composition time - also builders have several thousands of years of tradition, programmers have less than a hundred.

Actually it's the Windows 10 of software. Which is the problem: if you hire a builder or a plumber and they do something stupid which causes you significant harm, you can sue them. And you'll probably win. If you buy a car and it's defective and causes you significant harm, you'll likely get compensation from a class action suit. How did destructive software errors get an exemption from the legal principle of accountability? (I know the EULAs say whatever, but that doesn't mean they can't be challenged in court.) Adobe, MS, Apple and the rest don't need to care about software quality because they don't need to worry about expensive legal action by customers. Stupid crap like this will continue to happen until that changes.

Nutmog 11y ago
I think it's fair to put the blame for data loss on users as long as it isn't done maliciously. That's because users are the ones in the best position to protect against it by making backups in proportion to how valuable their data is. It would be a nightmare if Adobe had to make a backup of every customer's computer just in case their software had a bug that deleted something. Much more efficient for the user to just have a single backup protecting them from bugs in all their software rather than all their software redundantly doing it.
AsyncAwait 11y ago
I agree that some stronger regulation may be needed, but applying a broad "punish for a bug" strategy will have terrible effects for our industry as it will lead to a stagnation in innovation and a reluctancy to experiment. (We can already see this with the "Error 53" bug, where Apple is actually doing the right thing by not letting the secure enclave be compromised and getting sued for it). Look, bugs in software are as old as software itself, comparing software to a builder is not helpful because it is simply not the same thing at all - software is a lot more abstract and the effects of doing certain things are far less measurable at composition time - also builders have several thousands of years of tradition, programmers have less than a hundred.