I don't believe that Apple design their stuff with the intention to make it hard to repair for end users, but rather that they make trade-offs that improve other things with the cost of making user repairs hard. But I might be wrong...
I don't believe that Apple design their stuff with the intention to make it hard to repair for end users, but rather that they make trade-offs that improve other things with the cost of making user repairs hard. But I might be wrong...
The problem is lack of genuine replacement parts, lack of (legally available) schematics and other technical documentation, and software/firmware that prevents repairs by bricking devices [1].
[1] - https://www.macrumors.com/2016/02/11/apple-facing-error-53-c...
This is already not true for independent auto repair shops. Manufacturer specific computer diagnostic tools can cost them tens of thousands each and often they don't have the same level of tools as the dealers.
The tools themselves aren't the issue, the only thing specific to these tools is a complete mapping of proprietary error codes. If manufacturers were forced to release a list of all error codes and their meanings as part of the owner's manual this would be a non-issue.
Maybe a few things aren't "genuine", like finding OEM batteries is pretty tricky with some devices, but the ones you get do the job with no significant issues in my experience - just beware of the risks of faked specs and buy the cheapest rather than paying more for faked spec.
The thing about repair is it's often not economically viable, especially if you're paying for labor - for example, I could have payed someone $100 to replace the phone screen on my Nexus 5 - a brand new one on ebay goes for $170. I may as well just buy a new phone or use it as an excuse to upgrade. So in many ways, the repair shops are a bigger impedance to repairs than the parts situation in my opinion. Instead I was able to buy a replacement screen assembly directly out of China for $30 and do the replacement myself for free, it's the only way the repair made economic sense.
However, I think the main purpose here is to make spare parts available for the people who really want to try. Designing for repairability in mind is such a vague concept that Apple & Co. will be able to legally weasel out of it anyway.
I know upgradeability isn't exactly the same as repairability, but they're close.
It's not as you can't buy a computer thats easily upgradeable (every PC ever almost) if you would like to made that trade-off yourself. (Again I would also like to see an upgradeable iMac / cheaper Mac Pro)
(In my specific case, as an iOS developer, I can't buy anything but a Mac.)
And don't take me wrong, I would looove a more upgradeable Mac (also an iOS developer), but I feel that Apple should be allowed to make those choices by themselves. If upgradeability would be so important for me I could always be an .NET-dev.
In my assessment, Apple hasn't make the right decisions when left to themselves. And it's not just me saying that. Even some Apple fans are saying so: https://marco.org/2017/04/15/mac-pro-audacity-of-yes
You're still free to disagree, but in that case we should agree to disagree.
Economics textbooks assume there are an infinite number of suppliers to choose from, but in reality there's often only two or three, so "do something else" isn't often an option.
Edit: also do you have any thoughts on the idea of legislation forcing you to maintain an old app? There's a Go game scoring app I use on android but it's buggy as hell, not as good as it used to be, as far as I can tell the developer keeps some servers on but hasn't updated it for a very long time. Should there be a law requiring him to keep the servers on? I can't use anything else on android (that I know of), I'd have to develop it myself.
How much did you pay for that app? A few dollars? For that money, it's not realistic, given the economics, to expect support for a defined period of time. Enterprise contracts, as an example, do have a defined support period but are much costlier. Or you can outsource the development, or buy the app from the developer, all of which are much costlier than a few dollars. Or write it yourself, which is again much costlier in your time. It's simply not financially viable to guarantee that for a few dollars.
Instead, it's more like a one-time thing: you buy what is offered today. There's no promise of updates. Heck, there isn't even a promise that the developer will keep the servers running. If the business isn't working out, despite the developer trying everything possible to make it work, the only option is to shut it down, which is no different from other businesses. This is the unfortunate reality.
I wouldn't, and I hope Apple finds a way out of compromising its standards for the sake of random European regulations.
Despite that, I don't think requiring specialized tools is a problem so long as they are (1) generally available and (2) reasonably priced.
Let's hope they don't use those.
Simply because there's like 3 or 4 other types out there which look really, really close to a phillips, but aren't. They have slightly different shapes, and use different shaped bits/points on a screwdriver. Some are compatible with each other (but none are compatible with all!) - and others, if you use the wrong driver on the wrong screw, will tend to strip it out, or cam out with damage to either the screw, the tool, or both.
There are much better yet still easy to obtain drive profiles out there to use for screws (torx is one of them).