Slashdot Mirror
When Software Leaks (and What Really Goes Down)
Bryant writes "The Windows community is somewhat notorious for leaks from upcoming versions of Windows (obligatory link to this guy since that's most of what he does), and while the official PR word from Microsoft and many other companies with regards to leaks is a simple 'no comment,' no one has really gotten a candid, inside look at the various things that go down when word, screenshots, or builds of upcoming software leak. I managed to get some time with a senior Microsoft employee for the sake of discussing leaks, and the conclusions reached (leaks heavily affect communication, not so much the product schedule) as well as what these guys actually have to deal with whenever someone leaks a build, breaks an embargo, etc. may actually be a surprise given what most companies try to instill in the public mind."
I think they still are, this guy was talking about unplanned leaks, which would mean that there are also planned leaks.
See, this statement is logically flawed.
If you knew about it, and told us it existed, then it would not in fact be "secrete" and thus not exist. Your absense of knowledge of this "super secrete" committee is similarly in no way prove of it's nonexistance. Furthermore, if the the committee does in fact exist and you are aware of it, then you denying its existance would be expected.
"linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
It's not like Microsoft's "leaks" are anything new. I have even found references on old archived newsgroups to people discussing pre-release Windows 1.0 as early as late 1983 (although perhaps not "leaked" if they were meant to have it). Late 1983 was when Microsoft was promoting this vapor-ware product in magazines such as Byte in order to upstage the now forgotten VisiCorp Visi On and this little product about to be announced from Apple called the Macintosh. Of course it was not officially release until 1985. There is even a late 1984 pre-release still floating around.
Microsoft wants people to get their hands on their software. They make it available to developers, testers, and reviewers. And if they wave their hand to others and say "ah-ah-ah you aren't allowed to have that" then people start drooling over this tempting forbidden software rather than seeing it as just another pile of bits. It is an inexpensive way to produce publicity.
That's what PowerPoint is for. You have to speak to them in their own language (i.e. pictures and text so simple as to be inaccurate) ;)
Compare to Linux, for example, where "leaking an unfinished build" is a total non-issue. Even expected, in fact. So whether the leaks are intentional or not, if they are a problem, then it sounds like they're a problem of Microsoft's own making.
Breakfast served all day!