"Bah, it's revenue that matters"
October 2010: revenue(AAPL) > revenue(MSFT)
"Bah, profit is the real metric"
April 2011: profit(AAPL) > profit(MSFT)
"Bah, basic research is where it's at!"
I agree that Microsoft has done a lot of great research, and I hope that some day they can turn more of it into products. Alas, from reading the pub directory at llvm.org, for example, I get the impression that when something similar to Bartok & Singularity become products for real users they're going to come from elsewhere.
Time will tell, though.
I do love my Kinect.
After all, we need to nip it in the bud before even a seemingly innocent comment can set the precedent that Apple criticism is acceptable.
Most people I've talked to who worked elsewhere are shocked at how small the teams at Apple are.
Unless you're going to say there are only 15 people on iOS. In which case I will be seriously impressed!
Oh, and if you want an Apples to Apples comparison...I was there when the Server group merged with the Dev Tools group...and the merged group is maybe 300 engineers total (all of server was about 70 engineers...all told OS X and iOS combined only comes to something like 3000 engineers).
A fun little link: http://www.wolframalpha.com/input/?i=revenue+per+employee+at...
That sounds about right. For Win7 about 2500 engineers (1000 devs, 1000 testers, 500 PMs). I suspect WP7 is probably 500 engineers. So Windows + WP7 is probably right around the same number.
Interesting to think that in terms of products where Apple and MS compete directly, they probably have very similar headcounts. There's a mythology that MS is this huge beast that will crush you (at least in the past). But in reality MS ships 100+ different products. The company is spread a lot thinner than lay people might imagine.
http://www.pc-wholesale.com/networking-news-a-small-army-of-...
This sounds funny from my POV because I work mostly with startups now so I'm usually 0-1 levels away from the CEO. In the last 2 weeks alone I've ended up in F2F conversations with folks who I originally thought were some bizdev guy, perhaps a senior technical architecht, but no, turns out, that was the CEO. (... ", bitch." <--- per The Social Network) I was in a conversation the other day with a guy who was the CEO of a potential competitor, but at the time I didn't know he was the CEO, or that they were a potential competitor, and likewise in reverse. Funny stuff.
So yeah, this whole "flat company" with a mere 5-8 levels of hierarchy, makes me giggle. Back to my Terminal session, which this CEO considers his office. :)
(not criticising, just pointing out the humor of relative POV's)
I've always felt they spent so much on "research", in part, as a way to reduce their reported profits. Because Microsoft was notorious for mostly just copying what others did first (see Apple --- and yes I know about Xerox PARC), or acquiring/rebranding/integrating (Spyglass -> IE, etc.), and only a small percentage of so-called original/in-house stuff. When the original version of C# and .NET came out it was so hilariously obvious what they were ripping off at that time (cough-Java-cough), they didn't quite shave off all the boilerplate for those in the know. But They Capitalized Differently. Oooooh. ;)
On a related note, I once knew someone who officially worked in software R&D. And I noted they mostly spent a lot of time surfing the web and then parroting some sexy sounding thing they read about recently. Ironically (or not?) I think that's a not un-legitimate way, and certainly can be an effective way, to introduce new thinking inside a particular company, or introduce a new technology, like say as a pilot project. But to describe this process as requiring heavy spending (on software R&D mind you, not talking about hardware stuff) sounds ridiculous and an unnecessary money sink. Find a smart creative engineer. Take them off the leash. See where they go, what shiny nuggets they bring back. That's how you do practical software R&D, outside of academia. Doesn't require billions. Just brains, and it can be a side product of what your staff is already doing anyway -- if you have the right staff.