Gary - <Remember that it is said that 4 .18 FAB has been ramping.>
In various stages of readiness, they still are.
<Unfortunately, I hold a much higher standard for Intel than AMD.>
For this incident, when it became apparent that our commitment 3.5 months from now was in jeopardy, Intel told the world. I wish we didn't have the technical difficulty that caused the slip, but we did. The problem just recently became apparent. There was very little time between discovery and disclosure. I don't know what else could have been done, except turn back time and road map a November release date, or have the issue magically go away.
Again, you have every right to be disappointed, mad, whatever that there was a slip. However, Intel management acted properly in this circumstance, IMO. I know virtually 100% of the issues involved here, and if I were running things, I would have made the announcement at the same time they did, because before yesterday there was not enough data to tip the scales, but after yesterday there was enough evidence to suggest the target was in jeopardy.
PB |
