> Where's (4) Don't write slow software?
Says who, the government? We are talking about court-imposed fines here, not consumer wishes. Do we want a literal slow-software police?
Says who, the government? We are talking about court-imposed fines here, not consumer wishes. Do we want a literal slow-software police?
That obvious answer is no, but as I think back on how many times I've been frustrated by some poorly performing piece of shit application over the past year, it's starting to not seem so bad of a solution.
This court case shows that we kinda now already have one.
The phones from 5 years ago already had amazing processors with billions of cycles per second. They can probably do nearly everything.
But you know us software engineers: "make it faster till it runs wells on my test kit, then oh well ship it!"
I think this ruling is a nudge into a better way. Yes deplay updates for more than 2 years, but don't stop optimizing new stuff when the latest phone can run it pretty well - keep optimizing until devices from the last 5 years run it very well.
That's patently wrong. The point of the fine was not that the phones were noticeably slower after the upgrade. The point of the fine was that the slowness was motivated as a way of inducing forced obsolescence. The manufacturers forced the updates with no rollback mechanism to render phones unusable and thus force their users to purchase replacements. If users could roll back the changes then the manufacturers wouldnt be fined.
Yes please!