|
|
|
|
|
by MatthewPhillips
5391 days ago
|
|
I'm not anti-iOS, I'm anti-all current mobile OSes. I think you present a false dichotomy. I shouldn't have to know how the engine in my car works, but I should have the option of tinkering with it if I wish. And I do expect my car to be componentized. I expect it to have a transmission, an alternator, a radiator, etc. While I have no preferences for how those components are designed, I expect them to work, on the whole, as one would expect those types of components to work. That is they have an input and output. I wouldn't buy a car where all of these components were replaced with 1 proprietary, untinkerable, thing. What I want is Canonical or Mozilla, or whoever, to be able to write an OS that can be installed on just about any phone hardware, the way it can be done on any x86 computer. Whether it's the crazy patent situation or harder engineering challenges that prevent that today, I'm not sure. |
|
But in practice, as systems exhibit more of those traits more strongly, they, as a general rule, become less and less of a coherent, unified whole and more of the internal workings become exposed to the user. This has a direct impact on usability.
Until somebody resolves this seemingly-fundamental engineering constraint, we'll have to settle for different systems that varyingly trade-off flexibility and usability. iOS has been so successful because Apple has deliberately chosen to fall more on the usability side and a tremendous number of users have found that the tradeoff is worth it: that decreased flexibility doesn't harm them remotely as much as poorer usability would. Happily, there are also extremely flexible systems available.
Looks to me like this setup allows everybody to win as much as we know how to in this "imperfect world".