@Horash... "I was trying to be skeptical about it..."
Don't be skeptical about it....Microsoft has only one raison d'etre and that's to make money off us. Given the installed base of happy XP users, they could easily keep up security updates and maybe get an updated version of IE that works with XP. But that would cost them money and not bring any in. Maybe they should have charged $20 a year for support, I'd have paid that. But they have given me the most powerful incentive yet to look more at Linux.....
I was trying to be skeptical about it but the more I read about this topic, the more I deem this thought to be true. There are still tons of users on XP who cannot upgrade for a number of reasons, legacy software being one of them. Microsoft has clearly moved on, but the users have not. Companies have had to come up with solutions to protect Windows XP users. One example of this is Rollback XP, an instant recovery software for XP users that will protect them from viruses and other forms of malware. It is even being offered for free.
So I just found out that one of our "utilities" we sell electrical equipment to still is on XP. And its one of the most security focused utilities we sell to. We provide a mini SCADA system to them as well. Right now we are trying to provide LDAP authentification to correspond with SCADA yet they are still on XP wow.
That's interesting. I don't remember those particulars anymore.
The apps that I was involved in were ports of programs from the I-B-M Sys 3X machines, mostly written in either RPG or I-B-M mainframe BASIC. There was a company that had developed a quasi-compiler whch could take this source code, tokenize it, and run it on PC products. It was usable either as a standalone PC, or a NOVELL-connected network. It was an ideal solution for small to medium enterprises which had considerable investment in custom applications software to directly port over NOT ONLY the data files, but also the program files. This "environment" was so powerful that it supported INDEX file generation, expanded SORTing functions, etc. The BIGGEST hassle was in converting the I-B-M format files (with PD data types) from EBCDIC to ASCII, and transferring the files from the larger machines to the PC, since there was little to no convenient method to go from an I-B-M 8" diskette to the PC's 5 1/4" or 3 1/2" diskettes. But, we're talking about the 1980s & early 1990s, so that's eons ago in the Wacky world of Computerdom.
Very solid operating system indeed. What I used it for was to develop DOS netware applications in their VMs that worked. While others were fudging with QEMM and the like in DOS, I was developing multi-user DOS apps that used private netware connections (i.e. each one required its own Netware license) in virtual isolated DOS instances, each with varying configurations. Some "machines" had SVGA, VGA, EGA (remember EGA?), more/less colors, more less RAM. OS/2 was in fact the very best solution for developing DOS applications in the day - and in no case did a DOS operating instance affect the OS/2 host.
One thing that hurt OS/2 adoption was the weird thing about how the 486/Pentium turbo mode needed to be turned off when installing the OS. People could not see WHY or HOW there was any difference - after all - most operating systems do not have a kernel alignment during install. If the turbo mode was left on during installation, OS/2 would until reinstalled trap randomly which frustrated many a developer who blamed their tools (which were excellent). Leaving turbo mode off during installation when people bothered to try, however, allowed one to experience OS/2 as it was meant.
"Furthermore, I think, ATMs have no internet connections."
I would assume the same thing, otherwise they would've been hacked long ago, with or without MS support of XP.
On the other hand, banks do have internet connections that allow remote electronic banking from any internet-connected device, including your smartphone. To my knowledge, there have been no widespread security problems with that...yet.
During that period when I-B-M was "fighting" MICROSOFT for superiority of multitasking PC opsys, I was involved with an applications development team who demonstrated a MULTI-USER version of OS/2. There was a multi-day conference of applications developers for end-users of this programming environment. Repeatedly, the folks demonstrating their program running under MULTI-USER OS/2 ran seriously errant programs in order to impress the attendees that forcibly causing an app to crash DID NOT shut down the entire OS/2 environment. Other apps, whether the main one, or word processing programs or LOTUS 1-2-3 continue to run UNAFFECTED in their own windows! Not once during this conference were they able to force OS/2 into a "GENERAL PROTECTION FAULT", etc. mode.
Than I-B-M "surrendered" to WINDOWS & MICROSOFT by ceasing distribution of OS/2 will go down in the history books of Computer Operating Systems as one of the BIGGEST failures in effective marketing since the dawn of the Age of Abacus!
While I realize your comment was made in jest, I wholeheartedly agree with the concept behind it. Sometimes (Many times) I believe engineering efforts & the results are done solely for the exercise of engineering, and NOT for the betterment of the consuming public.
Believe it or not, but we have an MS-DOS PC at home (actually have a couple working units) which we use for one application. Many years ago, there was a program called MANAGING YOUR MONEY by Andrew Tobias. It's a GREAT program for managing home finances, even includes a lot of "advanced" features for folks who have a considerable investment portfolio. And, it includes links to I-R-S schedules, making the annual reporting process far easier. Obviously, this program is no longer supported AND the I-R-S features are out-of-date, BUT the basic GENERAL LEDGER-like format is invaluable in good record-keeping. Makes January a pleasure to live through. Finally, the ULTIMATE greatness of this program is that since it is MS-DOS, there's NO worry about viruses, malware, hacking of personal data, passwords, etc.
It's a real shame that under Balmer, MICROSOFT was not able to take a very introspective look at their main product, WINDOW XP, itemize its deficiences, & build on it as a solid, bullet-proof product. When they published VISTA, it didn't take but a few weeks for the consuming public to pan it to oblivion. One would have concluded that with VISTA being a debacle, they SHOULD have reverted to the core code of XP, and tightened it up, since it became THE MOST POPULAR operating system in history. But, NO!, they ambled aimlessly down a uncharted path. I guess we can only hope that the new CEO of MICROSOFT sees the errors in their ways, and efforts some significant corrective action. There's too many installations to ignore!!!
Thank you for hitting the nail on the head. XP Embedded support doesn't end until 1-JAN-2017. The effects are far wider sweeping than this makes them out to be due to the fact that things like built in SAN management workstations or even the underlying OSes can be XP embedded. EMC Mid range and I believe a few other people use XP embedded for some releases of the underlying OSes in their SANs.
In terms of there being issues with legacy OSes at the enterprise level, yes they will happen. A lot of the security risk is averted due to these systems being isolated because they are critical infrastructure, the same thing that makes them somewhat immutable and difficult to migrate off of as well.
If it an't broke why fix it. I work on machines built in the 1920s. They really knew how to engineer back then. Granted these instruments fade in and out of popularity. Factory support ended 50 years ago. Still they work and continue to entertain.
As I said before, I need special drivers which run custom real time protocols. Or dev tools which work only on Window$ because there are "Only 5 people in the world who use macs." and the vendor is too cheap to hire designers like myself who could port the software over.
It does not help that Apple removed Quicktime and MIDI support from Mavericks probably due to DRM issues. Now you have to "Render" MIDI through the audio engine. Of course no one complaines about apple, becouse well, they are perfect and make cool stuff that looks good.
Micro$oft is heading in this same direction. Closed hardware drivers and a machine that can only run the social networking app of the week. with lots of pretty colors and pentaphonic sound. It is the old television network "we know better than you, buy our soap because it is made with coal tar waste product and good for you." attitude.
If I had something like 40,000 man years to script and compile programs, such could probably be done with Linux. Effectively porting working windows95 real time code inside a kernel extension.
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.