Ha! Shame it wasn’t Win 7 that was released as I still use it on a few of my machines. ;-) Win 7 is the last MS OS that I now permit on my operational hardware. These days, Linux and rooted Google-free Android are my main OSes of choice.
Not that I care much nowadays, as XP's code release is unlikely to affect me in any practical sense other than for just curiosity to see what goes on beneath its surface.
Having experience with almost all Windows releases from the grotty, horrible Windows 1.0 of 1985 to the current Win 10, I've no doubt whatsoever the best and most practical version of the OS for me was Windows 2000, and from the numerous post I've read here many of you agree with me. (Incidentally, to be more precise, Win 3.1 for Workgroups was the first version I used in any practical sense as I found that Win 1.0, 2.0 and even 3.0 were essentially useless.)
My second choice is Win XP and it's still installed on one of my older working machines. In some ways, my next choice would likely be NT4, I had a lot of experience with it but once you got it working, which wasn't always easy, it was reasonably solid and straightforward to use. Of course, its major downfall was both the lack of drivers and not having any effective plug and play infrastructure (hence installing it was often messy and time consuming).
That said, I doubt this XP source code leak will be a unique event. I fully expect that we will see a great deal more source code becoming available from proprietary Windows-like software in the not-too-distant future—even if these 'leaks' do not originate from within the software companies in question (as all that will be needed is access to the compiled code).
There is little doubt that soon we will see competent deep-leaning AI disassemblers become available that will be able to learn how to disassemble large programs such as Windows with ease whilst simultaneously attributing its disassembled code with meaningful and intelligible code comments and descriptions. Moreover, I see little way that software manufacturers will be able to do to stop this from happening.
(I'd however add a caveat to the above, which is that whilst AI disassemblers will likely be able to eventually disassemble most existing compiled code that's been developed for past and present-day processors—from say the earliest 4004, 8085, 8051 and upwards to present-day ones as well as those likely to be developed in the immediate foreseeable future—this may not always remain the case, as it's possible that neither critical parts of compiled code nor newer specialized processor instruction sets may be available once manufacturers become aware of the threat.)
Furthermore, I'd wager it's likely that eventually AI disassemblers will actually learn on code such as this leaked Win XP. After all, what better sample would be available to a third-party AI developer or researcher to train his or her AI on than the source of the once-famous XP? None I suspect! Moreover, I'd add that I would be very surprised if companies of the likes of Microsoft and Google aren't already training their own AI on disassembling their own code. (After all, they've 'brilliant' examples to hand and a vested interest in seeing how capable AI is at the task of code disassembly—and moreover they need to know how much lead time they have before this new technology poses a serious threat to their existing products).
That said, with about a half century's worth of existing software compiled from many trillions of lines of code that will be available come the time AI is ready to examine and disassemble it, the snoopers among us will still have great scope! Frankly, I reckon the large-scale application of AI to code disassembly would be a truly great thing: just think of all the bugs and shitty bloated code we'll find. Moreover, exposing source code would put manufacturers on notice to improve their products—as not only would their multitudes of bugs and crappy code be exposed but also they wouldn’t be able to hide dirty tricks and corrupt practices as Volkswagen did with its engine emission technology.
AI disassemblers may even force many manufacturers to adopt the open-source model for their software development.
I've little doubt that over the long term code disassembly by AI will change the current paradigm of software development forever. Unlike its current undisciplined laissez faire approach to product development that encourages sloppy code full of bugs, software development will have to adapt to become a much more professional and rigorous engineering profession such as chemical or civil engineering both of which adhere to much stricter rules and disciplines—and I reckon that will be a good thing.
A more rigorous approach to software development is something I've advocated for many years—as I class myself a victim of poor software having lost thousands of hours of my valuable time—right, thousands of hours out of my life that would have otherwise been used to better purpose—resolving problems caused by poor, buggy and dysfunctional software—of which the majority thereof would never have occurred had standards comparable to those of other engineering professions been applied to software development. Given AI technology is of itself a product of software, and that it inevitably will be turned upon its own means of creation, seems to me to be poetic justice.
In the interim, I eagerly await revelations and 'meaty' pronouncements from eager XP code examiners.