4 ms·
"Starting with no copy/paste thru to maps." Not to mention the original intent to not support native 3rd party apps at all. Having said that, Microsoft really
by georgemcbay 12y ago
"Starting with no copy/paste thru to maps."
Not to mention the original intent to not support native 3rd party apps at all.
Having said that, Microsoft really did fuck up with the Metro (or whatever it is called now) rollout in stupidly trying to apply the same basic UI to everything despite the fact that it only works really well on touch-centric devices. And they've been stumbling a bit with hardware.. I'm not a Surface user but I do have an Xbox One and it is pretty disappointing compared to the PS4 (YMMV if you care about the live tv stuff, but as a "cord-cutter" I don't).
These slips really fucked up the user experience on desktops, laptops (via Windows 8) and consoles (the Xbox One console UX is in quite a lot of ways vastly inferior to the UX on the Xbox 360 and the primary reason seems to be to allow it to be yet another Metro platform).
However, there are pretty strong signals that the new leadership realizes this was a mistake and they are now attempting to fix it. It is way too soon to write Microsoft off as a major platform player.
- pohl 12y agoNot to mention the original intent to not support native 3rd party apps at all. Is there any support for this claim? The original developer story was to write web apps, sure, but how are we to know what the original intent was? It seems more likely that they were keeping their cards close to their chest while quietly polishing the SDK into a shippable condition.
- mhurron 12y agoApologists are only bad if they're MS apologists apparently. http://9to5mac.com/2011/10/21/jobs-original-vision-for-the-iphone-no-third-party-native-apps/ http://9to5mac.com/2011/10/21/jobs-original-vision-for-the-i...
- sjwright 12y agoIt has been Steve's modus operandi since the early eighties to make such statements in public and in private to stop customers and employees focusing on matters they shouldn't be. It was the right move to focus on releasing the iPhone without an SDK, and to distract the issue with the webkit "solution". It will have gotten the product out the door much, much faster than if they made it battle-hardened against third parties from day one. It's worth noting that the SDK was released just nine months after product launch and the full app store experience came within twelve months of launch. For a 1.0 release, the SDK was quite polished and surprisingly well documented -- hardly the product of a last minute change of heart.
- sjwright 12y agoDownvoted, huh. For future reference: Hacker News is only for the Android fanboys.