Apple could of allowed payment providers build payment services/plugins within their walled garden to preserve control and security. But they want their 30% so now the government is gonna come in and haphazardly create rules to enforce competition.
So a literal electric door lock would have the right to lock your door if they think you might break the copy right on the door lock you purchased from them.
Analogies are sometimes useful for understanding, but they rarely seem useful in marking an argument. It always seems redirect the argument into the ways that the analogy is different. (If the analogy weren't different, then it wouldn't be any clearer.)
If one goes into it with the intention of using the differences in the analogies to illuminate the domain, it can be helpful. But any argument of the form "X is like Y, and therefore since p(Y) is obvious then p(X) must also be true" is pretty much destined to shed little light but much heat.
I find an analogies useful in argument. They allow me to apply the logic someone is applying in an unfamiliar domain to a domain that is familiar to all, as a way of seeing how the logic holds up. Naturally, if the domains are too dissimilar, that becomes the focus of discussion. Like all tools, analogies can be used poorly.
Yep, I think the analogy would be better understood if it said they would stop the lock from functioning properly if the company had a suspicion that you were circumventing / reverse-engineering the lock.
If we could get the total cost of product disposal built into the checkout price. I think single use plastics would solve it's self along with a litany of other garbage disposal problems.
While I agree in principle, I don't think this quite solves it. For example, disposable bags are extremely cheap to dispose of - they compress well and would take up minimal landfill space. The problem is how many of them "escape" between the initial purchase and getting to the landfill. How do you include that in the cost?
Ideally this would be factored in and included in the cost of disposable. E.G. the cost of employing litter collection and disposal. The cost needs to be placed on the producers so they have incentive to solve these problems. Many plastic containers and recycling processes could be standardized but currently there's no reason to do.
The function call itself isn’t really the culprit (the cost of the function call itself is negligible in this case). It’s the implementation of the function [0].
It's not that people don't want to pay it's that it's difficult to pay small sums. The web browsers could solve this problem but they make money from ads so it's not in there best interest.
Jakob Nielsen's article "The Case for Micropayments" from 1998 still seems relevant. Nothing has really changed in 26 years so I'm skeptical whether it could ever work, but in principle it would be great for users and website owners to have that option.
They're likely record based formatting rather than file based. At the high level the code is just asking for a record number from a data set. The data set is managed including redundancy/ECC by the hardware of that storage device.
