4 ms·
What was it, _South Park_ that did the "Simpsons did it" episode? Thinking about some of the things that came along 20 or 30 years later remind of that. Virtual
by mikestew 13y ago
What was it, _South Park_ that did the "Simpsons did it" episode? Thinking about some of the things that came along 20 or 30 years later remind of that. Virtual machines? OS/360 did it. Virtual memory? OS/360 did it. Non-executable data? OS/360 did it. I was a security lead for a product while at Microsoft when the NX was being implemented, and wondered at the time why it took 35 years to get around to that. (I've never worked on a 360, but did some work its successor the 370 and OS/370 some many years ago.)
Even the Burroughs had multitasking before then, in the early 60s. And how can you not like a system with a "HEYU" instruction to interrupt other processors?
- da02 13y agoEver get an answer, or come close to one, as to why it took 35 years?
- cliffbean 13y agoBefore the Internet arrived, very few people had a big need for it. It makes some things marginally harder, and it's more work to implement, so it makes sense that it got left off. By the time the Internet generally arrived, and people generally realized what the Internet meant, we had accumulated enough backwards compatibility burden that sweeping architectural changes were difficult.
- mikestew 13y agoNever had access to those that could give an informed answer. As cliffban says, probably not much of a need. But if I had to pick a reason, and it would be a reason based on no inside knowledge, it's that the 8086 was a stop-gap design until the Intel iAPX 432 came out. The 432 had a lot of capabilities that mainframes took for granted, including segregation between data and executable code. Problem was that the 432 was so over-designed (which made it slow, for one problem) that it never saw production. So everyone just kind of settled on x86 and close to forty years later we're stuck with the 8086 legacy.