Cool! Corning has always amazed me as progressive company. One of my fist job interviews in the industry was on a cold February when they flew me to the city of Corning, NY, but after experiencing the weather I rejected the offer.
Microsoft made most of their money being able to upgrade people at regular intervals while maintaining compatibility with existing Apps and to a lesser degree use models. When they got to Vista they really broke this model, and it hurt them. I read last week that with W8 they are looking to use a java type model where all apps run as byte-code so they can reduce/eliminate developer effort when porting from one win platform to another. The plan is that if an app is developed for W8 it can run on a phone, a tablet or even across the web. Sounds good on the surface (pardon the pun) doesn't it? Well I recently upgraded a bit of SW that I use regularly to a java byte-code version and found that it ran like it was running on a 4.77MHz IBM-XT. It was woeful. Espewcially because I am running a Pentium i7 at 3.2GHz. I quickly downgraded to the old version. If this is to be the W8 experience then I will stick with XP and maybe W7 and finally when no W7 is available I will hopefully be able to migrate entirely to Linux because developer have realised what a dead end strategy it is. Also re the new tablet I/F, I use CAD programs extensively they are driven most accurately and quickly with a combination of keystrokes (on a real keyboard) and with a mouse/trackball/3D joystick, finger swipes just don't cut it.
:-) I use Ubuntu as a dual boot feature on my XP desktop. I like it a lot, so much more professional, less buggy and very snappy BUT: If my world revolved around an MSoffice type app and email an web I'd be on the Linux band wagon only. Sadly of the ~100 applications I use daily to make money only 2 are available under Linux. That leaves me and a large number of other people in the unenviable position of needing some flavour of Windows (see my other post below)
Microsoft is too large an operation to ever design an efficient OS. The competition has little to fear.
What is interesting is the tablet revolution. I took two years of typing in HS before I ever knew it would be useful for my career (CS degree). At the time it was predicted that typing was a skill that would not be needed by the time I got to the work force. That hasn't happened in the last 40 years. Instead the ASR33 became the input device for minis and later micros, followed by VDTs and then PCs, all with keyboards (QWERTY, no less--I learned DVORAK a bit once). With a little more effort, the keyboard may eventually not be an essential part of the personal computing experience. Certainly the tablet is a strong pointer in that direction, although it's present pop-up keyboard represents at least a temporary large step backward.
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.