Of course a major company downplays the significance of a smaller competitor buying a technology that they passed on. This isn't news, this is expected. News would be Intel expressing regrets that they didn't buy the technology when it was offered.
Well, you know in this business, the best defense, besides offense, is not to be defensive. That is why it is common for "no comments" to be a response. In this case, Intel could have spun it jokingly around to say "glad AMD has come around". Instead, it gave the message that even though you were once a supporter of Intel technology, Intel can turn its back on you, rather than help you develop.
KB +1 on that.
Sour grapes and likely a strong bit of not-invented-here (NIH) mentality from Intel's team. They have their own Xenon horse in the server race now - buying Seamicro might have been an acquisition disaster, ie, not enough room in the sandbox for two server chip design teams.
AKB3001- Possibly. I would have been a lot more surprised if she had said something like, "Yes, SeaMicron has great technology and we are kicking ourselves for not thinking of acquiring that company."
Still, I thought this was a particularly strong worded comment about a competitor's acquisition.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.