A spokesperson said that the only reason they didn’t open source Windows 3.0 and Windows 3.11 for Workgroups at the same time was that it was still in use for some highly critical systems.
Nah. Having worked in the industry - we built (the) Unix and a Linux distro, and I helped secure it - I can absolutely confirm older OSes are being used for very crucial stuff in an ironic mix of risk and safety that is bizarre.
Hint: Big grey-blue boats with numbers and famous names on the side.
Inside a janitors closet, behind 24 firewalls, is a single SPARCStation serving the internal financial information for GE.
A single chair is in the converted closet for Hank to sit when they (it could be one person, or three working in shifts, no one is really sure. But they respond to “Hank”) aren’t putting out the most recent fire. The pile of used extinguishers are replaced daily. Hank likes his job. Hank doesn’t like you. If you’re lucky enough and get access through the 7 biometrically locked doors to exchange the extinguishers, it’s been said you can hear mumblings from inside the closet about “uptime”.
On September 30th, 2018, John Flannery, the CEO at the time, asked why this was all necessary and considered replacing this system with something more modern.
"I joke with people and say it’s the Air Force’s oldest IT system. But it’s the age that provides that security,” Rossi said in an October interview. “You can’t hack something that doesn’t have an IP address. It’s a very unique system — it is old and it is very good.”
In 2016, the Government Accountability Office wrote that SACCS runs on an IBM Series/1 computer dating from the 1970s and that the Defense Department planned “to update its data storage solutions, port expansion processors, portable terminals and desktop terminals by the end of fiscal year 2017,” but it’s unclear whether those upgrades have occurred.
In new displays as well? Or are there some legacy considerations for the old displays that are still around?
I saw a Windows OOM error screen (something modern, win 10 at least) on my local transit providers in tram screen. One of them, the other 10 were working fine. That means that they each screen has its own os and hardware that needs to go with it.
How is that financially dependable or even practical to maintain?
Hardware solution: video signal splitter
Software solution: embedded controller board (pi1 would be good enough or some industry comparable product) for own os and software to run the information grabbed from the network. As images or as data that is then rendered.
I get that supporting legacy sucks. But it must be cheaper (not to mention easier and good on the brains for the it people) to get this stuff updated and kick it out. I kinda get it with banking mainframes and such but in this case there is nearly no risk involved when it goes down and needs to be fixed. And it went down anyways.
I bet there’s a not insignificant chunk of Win3.11 code still lurking at the heart of Windows even now. Patched and recompiled for 64 bits, but still there.
Though most of it is probably for backwards compatibility by this point. Or so we should hope.
An interesting assertion. A full install of 3.11 was about 8 MB or so, and all of the 8086 / -186 / -286 / -386 code will have been thrown away a long time ago. I doubt there’s much of PROGMAN left, and all the fonts and art assets are long superseded. So in terms of total code, it can’t be much. But on the other hand, the code that you write for an event loop or to handle driver interrupts hasn’t changed conceptually very much in that time. Most programmers would reimplement the basics in a very similar way, so there’s not much point in redoing it.
When I used to work in the water industry, we still had programmable logic controllers (PLCs) controlling pumpsets from the 1950s. The last person that could have modified them had retired and since died more than 30 years before. But deciding which pumps to run in order to best fill a reservoir is not logic that needs updating every day, not even every decade. Still working fine, don’t touch it. So I still laugh at my colleagues that can’t touch code that was written a few years ago in an unfashionable library. That’s not tech debt. Try, written by your grandparents for CPUs that had stopped being made before you were born.
And I remember 3.11 being perfectly good enough at the time, anyway. Wasn’t any Linux at that point.
A spokesperson said that the only reason they didn’t open source Windows 3.0 and Windows 3.11 for Workgroups at the same time was that it was still in use for some highly critical systems.
/s //Probably
Nah. Having worked in the industry - we built (the) Unix and a Linux distro, and I helped secure it - I can absolutely confirm older OSes are being used for very crucial stuff in an ironic mix of risk and safety that is bizarre.
Hint: Big grey-blue boats with numbers and famous names on the side.
Inside a janitors closet, behind 24 firewalls, is a single SPARCStation serving the internal financial information for GE.
A single chair is in the converted closet for Hank to sit when they (it could be one person, or three working in shifts, no one is really sure. But they respond to “Hank”) aren’t putting out the most recent fire. The pile of used extinguishers are replaced daily. Hank likes his job. Hank doesn’t like you. If you’re lucky enough and get access through the 7 biometrically locked doors to exchange the extinguishers, it’s been said you can hear mumblings from inside the closet about “uptime”.
On September 30th, 2018, John Flannery, the CEO at the time, asked why this was all necessary and considered replacing this system with something more modern.
https://www.c4isrnet.com/air/2019/10/17/the-us-nuclear-forces-dr-strangelove-era-messaging-system-finally-got-rid-of-its-floppy-disks/
Like, names of presidents? Dude.
3.11 is still used by Deutsche Bahn for display systems.
In new displays as well? Or are there some legacy considerations for the old displays that are still around?
I saw a Windows OOM error screen (something modern, win 10 at least) on my local transit providers in tram screen. One of them, the other 10 were working fine. That means that they each screen has its own os and hardware that needs to go with it.
How is that financially dependable or even practical to maintain? Hardware solution: video signal splitter Software solution: embedded controller board (pi1 would be good enough or some industry comparable product) for own os and software to run the information grabbed from the network. As images or as data that is then rendered.
I get that supporting legacy sucks. But it must be cheaper (not to mention easier and good on the brains for the it people) to get this stuff updated and kick it out. I kinda get it with banking mainframes and such but in this case there is nearly no risk involved when it goes down and needs to be fixed. And it went down anyways.
Most german thing I’ve heard today
I bet there’s a not insignificant chunk of Win3.11 code still lurking at the heart of Windows even now. Patched and recompiled for 64 bits, but still there.
Though most of it is probably for backwards compatibility by this point. Or so we should hope.
If you go deep enough, there’s still windows 3.11 dialog boxes in Windows 11 for some core functionality.
https://web.archive.org/web/20240102024352/https://ntdev.blog/2023/01/01/state-of-the-windows-how-many-layers-of-ui-inconsistencies-are-in-windows-11/
NOPE.
I last had to use the ODBC data sources file picker in 2016, so about ten years ago, in Win7. Completely forgot how much of a drag it was.
An interesting assertion. A full install of 3.11 was about 8 MB or so, and all of the 8086 / -186 / -286 / -386 code will have been thrown away a long time ago. I doubt there’s much of PROGMAN left, and all the fonts and art assets are long superseded. So in terms of total code, it can’t be much. But on the other hand, the code that you write for an event loop or to handle driver interrupts hasn’t changed conceptually very much in that time. Most programmers would reimplement the basics in a very similar way, so there’s not much point in redoing it.
When I used to work in the water industry, we still had programmable logic controllers (PLCs) controlling pumpsets from the 1950s. The last person that could have modified them had retired and since died more than 30 years before. But deciding which pumps to run in order to best fill a reservoir is not logic that needs updating every day, not even every decade. Still working fine, don’t touch it. So I still laugh at my colleagues that can’t touch code that was written a few years ago in an unfashionable library. That’s not tech debt. Try, written by your grandparents for CPUs that had stopped being made before you were born.
And I remember 3.11 being perfectly good enough at the time, anyway. Wasn’t any Linux at that point.
I’ve got equipment in the field thats from the early 90s. I imagine there’s plenty of computer driven shit that just works so never gets replaced.
The best part about shit that age is you can easily fix shit with some electronics or engineering skills.
😬