7 ms·
Microsoft is just not going to abandon Windows Phone, for fundamentally these reasons: "If it's a core business function – do it yourself, no matter what." ht
by SideburnsOfDoom 13y ago
Microsoft is just not going to abandon Windows Phone, for fundamentally these reasons:
"If it's a core business function – do it yourself, no matter what." http://www.codinghorror.com/blog/2008/10/programming-is-hard-lets-go-shopping.html http://www.codinghorror.com/blog/2008/10/programming-is-hard...
MS certainly will view "a computer in every pocket, and all of them running MS Software" as core to their future. If they do abandon Windows phone, it will be because that has changed.
In the meantime, MS is a company with a track record of plugging away until version x of the product is good enough to succeed.
- snom380 13y agoAgreed, although that track record stopped pretty much after IE and XBox.
- SideburnsOfDoom 13y agoIt's still happening, Azure is being iterated and improved a lot.
- fidotron 13y agoYou forget "Embrace, extend . . " The other mobile ecosystems are now so far in front they have no viable option other than the embracing and extending. Android happens to be flexible enough at the software layer (not just licensing) to make such a thing remarkably easy to do, given the resources.
- SideburnsOfDoom 13y ago> The other mobile ecosystems are now so far in front they have no viable option other than the embracing and extending. That's your opinion. I doubt that it would get any traction inside MS. It just doesn't make sense - are MS more likely to take the android kernel and reskin it to look like WinPhone, or continue to believe that writing OS kernels is a core company competence ... which it is, really. If one day MS could not write OS kernels any more they would be in serious trouble. It's a core business function, so they do it themselves. How would re-skinning android help MS get "in front" anyway? They have technically solid product in Windows Phone, they need other things to make it win, and they know it. Hence, the whole Nokia deal.
- fidotron 13y agoThere's almost no value add in a custom kernel from a customer perspective. MS don't so much sell Windows as Office, Exchange etc. These are whole platforms in and of themselves. Android is flexible enough to enable MS service clients to sit on top of it and act as if they're built in to the system, while getting easy portability for all the existing Android developers. (This is the point I think most objectors underestimate, since Android is a giant mess, but has an inspired way for plugging apps together at runtime). Windows as a standalone product is essentially dead, but selling it as part of a system for running Outlook, Exchange and Excel is not and won't be for a long while.
- SideburnsOfDoom 13y ago> There's almost no value add in a custom kernel from a customer perspective. MS don't so much sell Windows as Office, Exchange etc. True, the OS kernel is an enabler not a feature. > Windows as a standalone product is essentially dead And on the server world it's a platform for IIS servers, SQL servers, and azure clouds. Yes, a company that does this could decide to use someone else's OS kernel to enable all that. The original article that I linked to in grandparent comment explains why that would be a dangerous decision and is not going to happen.
- fidotron 13y agoI'm afraid your link merely shows the misguided point-of-view leading to the MS malaise. Look at your examples for server stuff: it would make no difference to the end user if those were running on Windows or not. IIS gets value from ease of .net application deployment, SQL server from playing well with .net, and Azure can deploy Linux because that department can't afford not to be in the embrace/extending mode. From an MS point of view making the OS might make these things easier to deploy, but just because you're good at doing something doesn't mean other people are going to keep paying you to do it, and so it will be with Windows. MS are going to end up disadvantaging themselves given they have to duplicate a lot of work going on in the open source community. If you use Chrome in Metro mode on a Win8 machine you'll see the extent to which Google are outplaying MS, as it apes the Chrome OS experience completely. Google are leveraging the Windows user base to reduce friction to them eventually moving to Chrome OS.
- pjmlp 13y ago> You forget "Embrace, extend . . " Like Apple, Oracle, IBM and many other commercial vendors. Still don't get why only Microsoft gets bashed about it.
- fidotron 13y agoTo be clear, I'm not bashing - it's clearly a good business strategy, and confusing that current MS appears to have forgotten it. Google are currently showing how it's done perfectly.
- pjmlp 13y agoFaire enough, I just complained, because it is quite common in places like HN to bash Microsoft, while forgetin about similar practices done by other companies, just because they enjoy a few more geek points.
- mitchty 13y agoIts really only common because Microsoft did so well with it compared to the rest. Its not like we "forget" other companies do it, just that they haven't done nearly as well as microsoft in their heyday.
- gtirloni 13y agoWhen the next big thing comes and threatens Google, then we will see how well they will do. So far they raised and shined without much trouble.
- dasil003 13y ago"Embrace, extend" was more effective (and terrifying to competition) when Microsoft was the juggernaut. But now Microsoft is actually behind Google, so there's little chance they can extend it any meaningful way that would give them leverage against Google. Google has equal engineering resource and huge head-start in install base and ecosystem. So the real question is what could Microsoft leverage from AOSP? My instinct is they could probably build anything from AOSP into WinPhone far faster than they could utilize AOSP directly.
- tc104 13y agoMicrosoft have always been an IBM 2.0 in the making. They were just waiting for a competitor to come along and show their stuff up as the tacky, badly designed garbage it always was.
- fidotron 13y agoYour instincts are wrong, but I've run into this misconception a lot. Nokia made this error, and RIM/Blackberry are doing it all over again. All they have to do to use AOSP is 1. start using it, 2. develop apps which are clients for their services, and 3. release a device with those clients preinstalled. There is no magic hidden step. Everything from the accounts system, inter app communication, billing, push, is pluggable and they already have the servers for most of it setup, which is far and away the hardest part.
- dasil003 13y agoI'm not sure what misconception your think I have, but it has nothing to do with how easy or hard AOSP is to use. It's the fact that Microsoft already has a good mobile phone OS tied into their ecosystem. What does AOSP bring to the table that is going to move the needle for them?
- pjc50 13y agoYes, but what does that benefit them? There's very little money in being an Android reseller, even if you're driving traffic to your services.
- brudgers 13y agoEmbrace extend works for markets and technologies not so much for operating systems. Nobody has done well embracing and extending Android, those who tried such as Samsung are throwing in the towel because of... ...wait for it... ...you know it's coming... ...vendor lock-in. I think the article gives Android too much credit for mindshare. Sure it's a platform for developers (this is why the monkey boy criticism of Ballmer makes no sense) but it's not really a brand among consumers. In consumer minds, Android is simply not an iPhone and increasingly not a Windows Phone. All that manufacturer and carrier customization erodes the idea of Android. In so far as Android is a brand, it's Google, not Andorid. But the primary brand of an Android phone is the Phone's manufacturer. Doing Apple on the cheap doesn't work.
- guiambros 13y agoIsn't Kindle Fire OS a perfect example of embrace and extend? Sure, it's also vendor lock in, but a good example that you can fork Android without relying on Google's services.
- Roboprog 13y agoHmm. What if MS made a .NET to dex converter??? I'm in the MS hating camp, BUT, I suppose they could actually devote enough resources to make a quite usable mode in Visual Studio that supports a .NET subset that maps to the Android/base API and then translates .NET bytecode to dex/dalvik format. Oh, the horror...
- halter73 13y agoXamarin allows you to use Visual Studio and .NET/Mono to target Android and other platforms. [1] dot42 focuses on Android exclusively and targets dex/dalvik instead of the Mono runtime. [2] [1] http://xamarin.com/ http://xamarin.com/ [2] https://www.dot42.com https://www.dot42.com
- sirkneeland 13y ago"all of them running MS software" is already never going to happen. If they view that as core to their future, they have already failed. What needs to happen is that the definition of "running MS software" needs to change from an OS stack (where they've already lost) to things going on in the cloud.
- gtirloni 13y agoI don't think that battle is settled (or that it will have winners and losers at all).
- SideburnsOfDoom 13y agoI don't think it's quite that settled. And no, it's not just about the OS stack. It says something that MS's new CEO, Satya Nadella, used to run the cloud group.