So what does a modern ATC look like? can winehq save the day in the interim or in the transition?
If anyone knows what ATC software they are using in the wild, let me know. A screenshot would suffice.
11–20 of 197 posts
So what does a modern ATC look like? can winehq save the day in the interim or in the transition?
If anyone knows what ATC software they are using in the wild, let me know. A screenshot would suffice.
> This is the most important infrastructure project that we’ve had in this country for decades. Everyone agrees — this is non-partisan. Everyone knows we have to do it. Considering the current political climate and rampant government cuts to important services, I very much doubt “everyone agrees” and that this is the best time to be planning such an important transition.
A first step to mitigate some of the risk would be to move the system to a virtualised system. This could be in each location or more centralised which would make the maintenance of the fleet of old computers easier. Floppy can be copied to hard disks and will not have to worry about failures of mechanical parts involved in reading floppy drives. Developing a brand new system would take quit a lot of time. As all sys…
> This is the most important infrastructure project that we’ve had in this country for decades. Everyone agrees — this is non-partisan. Everyone knows we have to do it. Considering the current political climate and rampant government cuts to important services, I very much doubt “everyone agrees” and that this is the best time to be planning such an important transition.
> This is the most important infrastructure project that we’ve had in this country for decades. Everyone agrees — this is non-partisan. Everyone knows we have to do it. Considering the current political climate and rampant government cuts to important services, I very much doubt “everyone agrees” and that this is the best time to be planning such an important transition.
Of course, that's why he had to say those words in the first place
It’s about as effective as placing a monkey in a porcelain shop then walking away while commenting loudly “Now now, it is very important none of the porcelain breaks, everyone knows it must remain intact”. The monkey doesn’t give a shit.
Butchering a proverb: “The best time to reorganise your porcelain store was before you bought a monkey. The second best time is after you sell the monkey.”
A first step to mitigate some of the risk would be to move the system to a virtualised system. This could be in each location or more centralised which would make the maintenance of the fleet of old computers easier. Floppy can be copied to hard disks and will not have to worry about failures of mechanical parts involved in reading floppy drives. Developing a brand new system would take quit a lot of time. As all sys…
Virtualization just adds another layer of complexity to an already fragile system which literally thousands of human lives depend on every day. Adding more complexity is not a neutral act here, but neglectful manslaughter waiting to happen. Aviation is a low-tech, never-touch-a-running-system, risk-averse environment for a reason.
Floppies were useful because you could easily take them and take them to another, secondary, sometimes air gapped backup system. Replacing this functionality means replicating not just the data transfer, but also the safety architecture - which includes physical isolation and manual fallback paths. To recreate, the best chance would probably be something like storing the relevant info on thumb drives - but then you have whole new family of attack vectors by hostile forces (anyone still remember Stuxnet), which floppies did not have in that form?
And then there's the pesky aspect of international interoperability. One country alone cannot just storm forward. We are looking at decades of upgrades and alignments here. And that process already is underway. But proposing a radical change without acknowledging the full scope of what that entails - from certification cycles to human factors to geopolitical coordination - is not progress, it’s hubris.
Earlier quoted context omitted.
Of course, that's why he had to say those words in the first place
And then what? Those words mean nothing to the people with the most power and motivation (or lack of care) to derail the whole thing. It’s about as effective as placing a monkey in a porcelain shop then walking away while commenting loudly “Now now, it is very important none of the porcelain breaks, everyone knows it must remain intact”. The monkey doesn’t give a shit. Butchering a proverb: “The best time to reorgani…
Earlier quoted context omitted.
And then what? Those words mean nothing to the people with the most power and motivation (or lack of care) to derail the whole thing. It’s about as effective as placing a monkey in a porcelain shop then walking away while commenting loudly “Now now, it is very important none of the porcelain breaks, everyone knows it must remain intact”. The monkey doesn’t give a shit. Butchering a proverb: “The best time to reorgani…
And then nothing? Do you seriously expect people to only say words that are effective at changing the world?
A first step to mitigate some of the risk would be to move the system to a virtualised system. This could be in each location or more centralised which would make the maintenance of the fleet of old computers easier. Floppy can be copied to hard disks and will not have to worry about failures of mechanical parts involved in reading floppy drives. Developing a brand new system would take quit a lot of time. As all sys…
We IT folks tend to quickly propose solutions to systems whose complexities we do not completely understand. That's fine when it is about serving ads or managing book orders. It's not ok when the stakes are high. Virtualization just adds another layer of complexity to an already fragile system which literally thousands of human lives depend on every day. Adding more complexity is not a neutral act here, but neglectfu…
"It's not broken" is the cry of the bad manager that hasn't done the proper analysis, hasn't actually looked at the pros and cons, but has simply become complacent and comfortable with the devil they know.
If they're still using physical floppies, then their process is broken now, so virtualising it will almost certainly un-break it.
A simple "clarifier" for this kind of thought process that I like to use is: If you were already using the new option (virtualised legacy hardware), would you think it a good idea to convert it to using open drives with convenient dust ingress, non-existent support and supply chain, glacially slow mechanical moving parts, and hilariously antiquated crunching noises for all data access? Would you? Really? Or would you recoil in horror at the very idea?
I use the same kind of logic on people who think staying on Windows Server 2012 in is a good idea. Would you downgrade Windows Server 2025 to 2012? Why not? You think it's a great platform, apparently!
PS: I worked on a large scale DOS-era software virtualisation project where we moved ~20K users onto a Windows + Citrix platform. We eliminated about 6000 floppy drives and about a million(!) tapes, and the resulting system was so much faster and reliable than the original that people were trying to bribe the project manager to be put at the front of the migration queue.