NYS is very business friendly. Especially if you're IBM.
And you can't hire any guy off the street to run your fab, so you're going to be paying them a reasonable wage, anyhow. So right-to-work doesn't equate to much in cost savings for this case. Plus, right-to-work states generally suck, you need to attract some good engineers - and most of us prefer the coastal states.
Intel knows what its got already. This gives them some access to IBM tech, which is probably a big net gain for INTC. The center of IBM tech dev is in upstate NY. Hence INTCs intent to go there. If it was in SiVly then IBM might get more out of it. Other sites are irrelevant.
One has to wonder how IBM and Intel picked NY. I mean, despite the fact of a "competition". (It doesn't matter how an electorate votes: what matters is who counts the votes.) Well, of course IBM would have a bias for NY, but I wonder if the state sweetened the deal on the taxes front. NY has not exactly been the "go to" state for business lately. If I were going to sink almost $5B in a business, I'd start out in some right-to-work state with a decent record on the business side of things.
Simple solution, you recruit in the spring and summer months, get the employee to move, ensure they sell their home and buy in NY, don't mention NY high taxes, or liberal state, then get them working before the first snow blizzard hits. On the flip side even Global Foundry has problems filling jobs in the region.
This is great for NY State. Too bad for unemployed engineers who are looking for a place to live with a good cultural offering with a lot of things to do. Winter in Upstate NY is rather depressing. I've lived in Rochester for 7 years and wasn't very fond of it. I also spent a winter in Binghamton which is even worse. But still this is a bit win for the NYS economy. Kind of wish this would happen in Portugal where I live now! :)
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.