Linked by Thom Holwerda on Sat 9th Feb 2013 18:54 UTC
Windows "The 16-bit Windows kernel was actually three kernels. One if you were using an 8086 processor, another if you were using an 80286 processor, and a third if you were using an 80386 processor. The 8086 kernel was a completely separate beast, but the 80286 and 80386 kernels shared a lot of code in common." As always, Raymond Chen delivers. If you don't yet follow his blog, you should. Right now. Click that bookmark or RSS button.
Thread beginning with comment 552190
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: On a side note
by Alfman on Tue 12th Feb 2013 02:08 UTC in reply to "RE[2]: On a side note"
Member since:


"The fact that Windows can completely change its kernel and graphical implementation without breaking most programs written 20+ years ago is nothing short of an engineering miracle."

I mostly agree, but it hasn't been completely smooth. Some of the stuff I wrote in VB in the 90s stopped working. Of course the only reason I found out was because I was poking around my early career archive for fun. Someone would need to test a large sample of software from that era to assess how well compatibility has held up in general.

Another article that was along these lines:

Reply Parent Score: 2

RE[4]: On a side note
by siride on Tue 12th Feb 2013 02:32 in reply to "RE[3]: On a side note"
siride Member since:

Keyword "mostly".

And, in any case, it's much better than compared to OS X or, especially, Linux. You have to rewrite programs written for different versions of the same GUI toolkit. The only thing you can really count on is the kernel interface and, to a greater or lesser extent, glibc's interface. Everything else is subject to change (and change it does).

Reply Parent Score: 3