Great article, getting to the meat of the matter, as it were. Having read this, even more so than in my response to the other Sinfosky article in EE Times, I'm curious about the future direction of Windows 8.
I guess that giving priority to the WinRT version of the Surface tablet was done to please the casual users soonest. But from my point of view, the x86 Surface is the one that would be most interesting and most distinguished from all the other tablets out there.
I agree with you, Bert, and I wouldn't be surprised if Microsoft now did a fair bit of bridge building with Intel. I think the Surface Pro, the x86 version, will ultimately end up being a winning device, and I can't help but feel that those who opt for the RT version will be disappointed. The apps they want won't work, and they'll wonder why they didn't just go Android. If you want a Windows tablet, it has to run windows apps properly. The Intel version will. I believe that by ousting Sinofsky, Microsoft will move closer to Intel again.
Windows RT is a must for Microsoft to not be bound by x86, which is very limited, almost nonexistent, currently in mobile non-PC markets. Windows 8 did not exclude Intel, so I don't know the big deal there.
From my perspective, Microsoft took a few things that tablets do well: reading, browsing and light weight gaming, without really understanding why the tablet has those features, and stuffed them into a PC OS. The 1985 era single application up at a time is largely due to the limitations of processing power in tablets. It's not there because people want to exclusively operate that way.
On a PC, it feels awkwardly hacked on without much thought for useability. It smells of a product designed based on the vision of an out of touch person.
If Sinofsky was that out of touch person providing the vision, then Microsoft and most of their customers will be better off with him being someplace else.
Microsoft is going in a new direction and putting their own way of doing things in areas that they really should stay out of. Who wants to have a buggy smartphone that needs constant updates? And what company needs a top officer in any area who does not understand about having all parts of the company work together at least a bit. So it is just as well to dump him, he certainly won't starve, or suffer any real hardship, no matter how long he is out of work.
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.