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."
Now people can rewrite the entire OS in "normal" C++ without all the awkward stuff like Active Objects, 10000 kinds of string "descriptors", CleanupStack and the weird API.
A single whack is not good enough. Repetition is very important. There has to be multiple severe whacks before everyone understands what's trully going on in this world. The implications of the Hubbert Peak on oil production is going to give us the opportunity for an enormous reality check. (i.e. we might want to care a little bit more about the fundamental things on which our society is build upon and change our way of life such that we live more in harmony with nature.)