I find it entirely credible that they wanted to make sure that nobody would cause another "incident" before the public announcement, and were willing to tell a little more than would be normal to do so.
| the majority of those people are not privy to
| the details
From the article: | internal Microsoft e-mail sent to all full-time
| employees working on the next Xbox
I'll concede that not all MS employees working on the next Xbox might need to know everything, but it's not like this was a broadcast to all MS employees to avoid employees from unrelated business units from running their mouths. | like that guy who got canned for talking about it on
| Twitter
Adam Orth was an exec in Microsoft's gaming division. He wasn't some random uninformed Microsoft intern shooting off his mouth on Twitter.This is not accurate. He was a (not the) Creative Director, which is several levels down the hierarchy from anyone that would be considered an executive. Think of it as one step above Senior Designer.
It's not a matter of being "privy" to the details. Just having the ability to get accurate information doesn't mean you'll bother to take advantage of that ability.
For all intents and purposes the console will mostly be used while online so this whole saga sounds to me like "anonymous sources" got their wires crossed to begin with.
Any way, this sort of email is very common in companies that involve hardware and software roadmaps, NDAs, etc. I don't think it's an insightful comment, and it's annoying when Ars Gawker-like promotes these comments for the sake of controversy.
That being said, I can imagine that it is still a possibility for game developers to use this tactic on the Xbox, just not a requirement. Doesn't seem like MSFT would gain much for wanting to force an always online connection.