While it is nice to say that IBM should put American interest first, it is too optimistic to think that they should have such a duty. After all, they are a business, and they would make decisions that would benefit them the most. I agree that it is controversial, but such things have been happening to many companies in America for years.
Jeanette - http://www.lyonessscamreview.com
I agree IBM can afford it
But why spend $2 or $3 billion on chip manufacturing R&D and "suffer" a profit of $16 billion when you could forego the expense and have a profit of $18 or $19 billion?
Unless chip manufacturing technology is strategic to the company (and the country?) that is?
A lot of other vertically integrated companies, such as Philips and Siemens in Europe and now we are seeing Hitachi, NEC and Mitsubishi in Japan are made different choices.
It doesn't make sense for IBM to sell its Fab. They can keep their proprietary design and Tech in house, and do not have to depend on a foundry for a supply & schedule of Tape outs.. They do not want a Qualcomm issue.
IBM Rev in 2011 was $107 Billion, spending 2-3 billion on research is not hard for them speacially when they pulled over $16 Billion in profit, some major Foundries, don't even have revenue of $16 Billion a year.
PC business is a low tech labor intensive business and does not require much CAPEX. Semiconductor still an high tech business(diversified fields and skills) with lots of CAPEX. Anyone can assembly PCs but only a few can still fabricate semiconductor.
But come on PC business continues to shrink and reduce into a small profit market now a days, so there is no comparison on these 2 distinct business strategies.
Exiting PC was overdue IMHO, but giving up the jewels overseas, with all the national defense projects and other high profile business. I do not see Intel, or other USA interest passing this up.
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.