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

Don't look for a change: their position was worse in the days of the Netburst dead-end and back then the company was just lucky that a second, independent path had been followed in the Haifa office to target a niche market (yes, laptops were niche in that age).

So has there been organizational dysfunction for decades? I think not: there are things Intel has always been doing very well and post-Netburst improvements after Core 2 have also been significant.

I believe that a big element is basically luck: you invest in a certain progression path and that investment will yield results so you keep going. Another path might be sufficiently better to write off the inferior path investment but you don't know that. Perhaps the unsatisfying path taken is the least bad of all. Even Netburst improved over time, a bit, and so did whatever forgettable AMD had been building between the Athlon glory days and those of Ryzen. As long as you see progress, it's very hard to just give it up for a fresh start (that may or may not be better). We can just be lucky that a luck/lock-in imbalance has never persisted long enough to make the lucky one the only survivor, because then they would never leave the left dead-end they'll inevitable run into some day.



> whatever forgettable AMD had been building between the Athlon glory days and those of Ryzen

Phenom II! I had six cores, 7 years ago! They were dog slow, but there were six of them (and that's all I could afford).


They weren't even that slow. Seven years ago they didn't win in __single threaded__ applications, but for any multi-threaded workload they were great.


How is that not equivalent to "they were so much cheaper that you could get more of them"? Hardly what I'd call architectural success.


It isn't always obvious for future workloads whether scaling out vs. scaling up will win.

And even when it is obvious for particular workloads, the relative value and demand of various future workloads is definitely non-obvious.




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

Search: