Is 18A delayed due to lack of resources, refusal to learn, or just overpromising for bonuses? It overpromised and underdelivered. Betting on ex-IBMers to build scalable, advanced tech was a gamble—GF let them go, Intel hired them, and it backfired. Expecting different results now? Good luck—I'm invested in 18A’s success too. Ironically, many of us predicted this 2–3 years ago and saw 14A as more likely to succeed by actually learning from past mistakes.
13 replies (most recent on top)
I don't believe OP rode such a short bus to school.
18A is DOA! 18A is DOA! Do da, do da
18A is what I like to call Intel's poster child for shareholder value destruction... wasted enough money to fund a small country to boot. 4Y5N never added up. Even if you could do it technically, the cost overlaps, load balancing across fabs, utilization and inventory headaches... Didn't anyone step and and show Pat the math? Even the US treasury can't print enough to fund that.
Intel will skip 18A and 14A because Pat was out for 4Y5N scam to jump straight into 10A to be leader again with 1N9Y
The promise of 18A is a scam. Even when/if it yields results, none of Intel's competitors will use it. It's all a big scam
Was Ann Kelleher misrepresenting and covering up?
18A confirmed 2035.
Panther Lake design is a dud! Not much performance gain, delayed massively and bad power consumption. The PTL and CWF/GNRD teams shd be let go first!
All anyone can say is. It better be good! If 18a/panther lake has any flaws or under performs to the customers expectations it’s is the END OF THE ROAD for Intel.
Overpromising for bonuses. It’s the Intel way of life.
lack of resources. Project haunted by the ghosts of layoffs past. Beyond that Intel management cannot estimate honestly how much it takes to finish a project or retain talent
Can't blame IBMers but 18A lessons could fill a few chapters in a book. Few years ago, foundry T feared Intel might execute it well and raise the bar for everyone—but the more customers engaged, the clearer it became how poorly things were going. Execution was slipping, and internal distrust between teams and organizations—an issue that needed top-level intervention—only made matters worse. Let's hope it becomes a turnaround story.
IBMers hahaha