The way I understand the history, Intel saw Itanium as the way forward and it had its advantages, not the least of which was the jettisoning of all the old x86 architectural baggage. However, backwards compatibility with all the old x86 software was high on everyone's priority list, and Itanium's performance at running legacy x86 code sucked. Badly. This was a major strike against it.
About that time AMD came out with x64 (they called it amd64), which is an evolution of x86 (code compatible with x86, breaking of the 4GB addressable memory barrier, simplification of some of the x86 segmentation architecture, and new additional machine registers which was always an x86 handicap, just to name a few). Intel resisted it at first, but then AMD started making inroads because x64 chips ran legacy x86 code at native speeds, and Intel was forced to follow suit. That was a major loss of face for Intel, which sees itself as the owner of x86 and AMD as an interloper.
Whenever Intel has listened to the market, they've usually delivered great things. When they tried to tell the market what it wanted, like with Itanium, not so much so. (think Rambus RDRAM too).
About that time AMD came out with x64 (they called it amd64), which is an evolution of x86 (code compatible with x86, breaking of the 4GB addressable memory barrier, simplification of some of the x86 segmentation architecture, and new additional machine registers which was always an x86 handicap, just to name a few). Intel resisted it at first, but then AMD started making inroads because x64 chips ran legacy x86 code at native speeds, and Intel was forced to follow suit. That was a major loss of face for Intel, which sees itself as the owner of x86 and AMD as an interloper.
Whenever Intel has listened to the market, they've usually delivered great things. When they tried to tell the market what it wanted, like with Itanium, not so much so. (think Rambus RDRAM too).
