We will allocate resources and build devices and services that provide compelling, integrated experiences across the many screens in our lives, with maximum return to shareholders.
We will allocate resources and build devices and services that provide compelling, integrated experiences across the many screens in our lives, with maximum return to shareholders.
Even if the corporation's main aim is to benefit its shareholders, that unnecessary line is going to come across as alienating to employees, who probably care very little about how these changes will affect wealthy shareholders.
http://www.microsoft.com/en-us/kinectforwindowsdev/newdevkit...
The say more than 50% of the Fortune 500 are now using Azure:
http://www.neowin.net/news/windows-azure-now-used-by-over-50...
These are fairly radical changes as they are getting off the desktop platform amd moving straight into the cloud.
That doesn't mean the article isn't technically accurate, of course, but I'd suspect that MSFT is being very generous with their definition of "using" and counting any pilot project in some engineering team as "using" - in which case I'm sure that most of the fortune 500 have someone somewhere playing with Azure.
But that's not the same as using from the standpoint that we typically think about it.
The way American/Chinese taxes work, actually, I'm annoyed to get stock at all as compensation and wish it would just come in as salary.
If you have something stupid to say, keep it to yourself.
Too bad you don't take your own advice. You would have saved yourself the embarrassment.
We will allocate resources ... with maximum return to shareholders
You have to imagine the meeting where they discussed this and someone thought that this sentence was going to sound to investors like a giant money pit. So in true committee style, they voted for a camel and stuck this odd phrase on the end to satisfy that person.
I would, if I could find any content in it. Still searching...
In other words, Ballmer realizes MS is a heavily siloed company, and that developing in silos is proving counterproductive to any serious attempt at cross-screen UX and platform integration.
How much of that is true, and how much of that is the spin being given to a cost-cutting reorg, is up for debate.