Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

To Intel's defense, there is a reason they resort to their approach of gradual improvements. In 1981, after a couple of successful iterations on their CPU, they did make a clean break with the past with iAPX 432 [1] - an entirely new 32-bit CPU designed to be programmed entirely in high-level languages. Hardly anyone seems to remember it, and for a reason: it failed, hard. Intel seems to have learned the lesson and didn't do this anymore.

[1] https://en.wikipedia.org/wiki/Intel_iAPX_432



A good point. I didn't cite it here because its implementation problems were severe and the reason it failed. Yet, I do give credit in more thorough discussions on INFOSEC history because the architecture was pretty awesome for Intel. Then, they watered that down with BiiN's i960MX. Then, even less radical (in security) Itanium. They lost hundreds of man years on the first, around a billion on second w/ Siemens, and at least $100 mil sunk into Itanium w/ HP.

Intel certainly tried to make up for their x86 monstrosity several times. They got smarter and smarter about how they did so in terms of market acceptance. A combination of engineering mistakes and foolish market choices (imho) made them pay. As you said, they learned to give customers the insecure garbage they wanted or risk extremely large losses. Links below for those interested in the specifics of their better work.

Intel i432 Capability System http://homes.cs.washington.edu/~levy/capabook/Chapter9.pdf

Intel/Siemens BiiN System (w/ i960MX manual) https://en.wikipedia.org/wiki/BiiN

Itanium Security Features http://www.intel.com/content/dam/www/public/us/en/documents/...


And then there was the i860 https://en.wikipedia.org/wiki/Intel_i860 (the original target for WinNT!), and later of course Itanium. Intel seems to have embraced the "x86 everywhere" vision much later than others (maybe 2004? http://www.anandtech.com/show/2493/4 ), only uttering the phrase in early 2008 http://www.computing.co.uk/ctg/news/1819476/intel-x86-future afaics. (Talk about awkward timing...)


Interesting, though this shouldn't be an indictment on HLAs in general, rather the iAPX 432 in particular. Same way the Mach server was only the tip of the iceberg in the sphere of microkernels.


True: the LISP machines, Wirth's Lilith w/ M-code processor, ASOS embedded Ada system, JOP embedded Java processor, and Azul Systems' Vega processors show HLA's can work just fine. Even better than competing offerings in ways. :)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: