3 ms·
Thinking about it further, I don't even think it's appropriate to call this "lock-in". I very much doubt the Apple engineers who wrote iMessage were rubbing th
by rosser 13y ago
Thinking about it further, I don't even think it's appropriate to call this "lock-in".
I very much doubt the Apple engineers who wrote iMessage were rubbing their hands together in maniacal glee, at the prospect of being able to prevent people from ever migrating away from iOS, if they but used the phone number in this specific way.
It sounds like it's exactly what TFA's author assumes: a bug.
- judk 13y agoSufficiently advanced incompetence is distinguishable from malice. Apple has certain well advertised priorities. Interoperability with non-Apple systems is not one of them. (Not to blame Apple in particular -- non-intropability is coincidentally a common feature among the biggest player in every industry, while interopability is a key feature of challengers. But it's just a "bug"... )
- hrktb 13y agoDoes it change much to focus on the original intention of the engineers? If the bug ever surfaced or was ever thought of by anyone at Apple at any point in the development process of iMessage, Apple will have effectively accepted to lock the user in by not having it fixed or communicate about it in some way. The OP must not be the first to report the problem either (he switched after iOS7, iMesssage was more almost two years old by then) ? This might not be an issue Apple cares in any way, and that's fine for them. We should just recognize their shitty behavior, even if it's originally accidental.