4 ms·
Sure, it's a good long-term strategy, but the replacement was immensely premature. See my comment further down the thread: https://news.ycombinator.com/item?id=
by cookiecaper 14y ago
Sure, it's a good long-term strategy, but the replacement was immensely premature. See my comment further down the thread: https://news.ycombinator.com/item?id=4577215 https://news.ycombinator.com/item?id=4577215 .
- tptacek 14y agoOne way to look at this: Apple is willing to pay, in eroded market share during the transition, for earlier control of their own mapping infrastructure. Again: isn't that a good thing?
- Locke1689 14y agoIt's certainly a daring thing. I suspect that you're right and that it won't be such a huge issue in a year or so. I do wonder if this is an opportunity for Microsoft to sell a complete platform experience while Apple is taking a breather. Disclaimer: I just recently started working for MSFT in a position not at all related to Windows Phone. I also don't own a Windows Phone.
- tptacek 14y agoI have a hard time believing Apple didn't see this coming. This isn't like Siri staggering under its load; the gaps in Apple's data, and moreover in the Maps feature set, are plainly obvious. Apple knew this was going to happen, and did it anyways. It is therefore part of a strategy.
- malvim 14y agoYes, that might well be a good move for Apple. We're talking "market share" and "control of infrastructure" and all that. That makes sense. One problem, though: It sucks that, in order to make a move that makes economic sense, you have to break stuff for your users. And not just break. REALLY break. Gruber talks about the options Apple had, and one is "wait one more year having less features than their competitors". Well, that sounds exactly like what Apple would do in the past, in order to have a better user experience. You know, the infamous "customers don't want this or that" that Jobs would always say when they didn't have something ready.