4 ms·
My intended audience is, I guess, anyone who's ever taken something apart in a bid to figure out how it works. The ability to put the thing back together again
by DrPizza 14y ago
My intended audience is, I guess, anyone who's ever taken something apart in a bid to figure out how it works. The ability to put the thing back together again such that the thing continues to work is strictly optional.
I hope it's deep enough that programmers who haven't been tracking Microsoft's efforts religiously will find it educational, but not so deep that someone who's merely interested in what makes the operating system tick is scared off.
- arscan 14y agoI expected this to be a short, mainly fluff 1 pager based on the title. I was pleasantly surprised when it wasn't. In order to pass judgement on MS's design choices for WinRT you really need to understand the history of the technologies involved. I think that this does a great job of doing just that. BTW, I fall into the "programmer who hasn't been religiously tracking MS" category.
- pkteison 14y agoThank you for writing it like this. Parts of it I was quite familiar with, but parts of it I have zero exposure to, and I really like being able to review the parts I already know as a way to check your credibility on the parts I know nothing about. Only thing I found lacking was I disagree with the characterization of the OS/2 split - 'forcing Microsoft...' seems to imply a backwards cause and effect from my understanding of things. But if that's the only nit I can pick in such a long detailed article, then it's darned well done.