And I have been on military projects that had to rewrite all the software because there were no compilers available for the target machines. One had to know both computer languages and operating systems much better than reading from a book. In fact one had to be an expert in both the old and new languages and operating systems.
While certainly an obstacle to the U.S. nuclear missile fleet being hacked, an old software language is not the reason it's immune. Vlad (and others) could certainly overcome such a challenge...."These are the computers that control the missiles, your phone has got much more power than them but these remain unhackable as most of their language has been forgotten"...
While certainly an obstacle to the U.S. nuclear missile fleet being hacked, an old software language is not the reason it's immune. Vlad (and others) could certainly overcome such a challenge.
The real reason U.S. nuclear missiles can't be hacked is that the control system is not Web based. Let's hope it stays that way.
Stupid emergency alarms though...
All US Air Force bases use the same hardware and software for their supply systems. In 1982, my first job out of college was converting the USAF Standard Base Supply System from the original Univac 1050 Assembler to Sperry Cobol/DMS1100. In the 1950's when the Air Force was procuring the original machines, they became obsolete before the contract ended and no commercial customer ever took delivery. The Assembly language for the 1050 was unique to that machine, so the only people who ever used it were a few enlisted personnel who worked at a central location and distributed code changes worldwide via tape. So for 30 years, the USAF continued to train a few people every year in this language and they used it for one purpose only.
1) A system has to be designed correctly.
2) The system must be thoroughly tested before connected to outside communication.
3) People have to be trained properly and on machines that are disconnected from sending out messages until the system is certified for service.
In that case the computers and assemblers still existed. I am talking about rehosting to different computers which do not have the compilers for the original programming language. Much different situations.
Do you think that a Minutemen system would need to be re-hosted to a new system?
Which kind of military project were you involved in, if I may ask?
I've used Linux in the past. Nice and all but there's a reason why the masses stick to Microsoft.
I used to be the masses. I tried Linux many times and was disappointed every time because the learning curve was too steep. But I tried again 2 years ago, the curve had flattened and I haven't used Windows since. I'm sure I will, but it will be because I have to. A job will require it. But I can't ever imagine going back to it for 99% of my personal computing. There is simply no reason to.
When there are many many more robust competitive Linux products with responsive paid support for high demand specialized applications then Linux applications will move much more into the mainstream.I used to be the masses. I tried Linux many times and was disappointed every time because the learning curve was too steep. But I tried again 2 years ago, the curve had flattened and I haven't used Windows since. I'm sure I will, but it will be because I have to. A job will require it. But I can't ever imagine going back to it for 99% of my personal computing. There is simply no reason to.
Two decades.... the Agfa Movie Camera film was phased out more like at least a decade ago by now.
Otherwise SkyNet will kill us all.While certainly an obstacle to the U.S. nuclear missile fleet being hacked, an old software language is not the reason it's immune. Vlad (and others) could certainly overcome such a challenge.
The real reason U.S. nuclear missiles can't be hacked is that the control system is not Web based. Let's hope it stays that way.
When there are many many more robust competitive Linux products with responsive paid support for high demand specialized applications then Linux applications will move much more into the mainstream.
Mainstream means flexible and adaptable support in a commercial environment. Our small office spent several hundreds of dollars each year for our application. Bigger firms would spend thousands per year. The value received for those dollars was excellent.
Too much of the Linux community expects software for free.
Not in any way connected to the missile command and control system. A state-based warning system effective at terrorizing the public, but incapable of launching anything. Fortunately.Stupid emergency alarms though...
Not in any way connected to the missile command and control system. A state-based warning system effective at terrorizing the public, but incapable of launching anything. Fortunately.
No, you do not have a need to know.
I don't disagree with what you are saying here (in both parts).I don't know if "mainstream" or "commercial" are prime goals of Linux developers or not. But its now a viable alternative for many if not most types of personal computing (so its more mainstream than it was), and certainly some commercial applications. More costly doesn't always mean "better."
Anyway, we should probably get back to the alleged reintroduction of Ektachrome.
if Linux is going to be viable in the long term for people other than just interested hobbyists, it needs to interface well with the world out there. .
And I'd bet a fair amount that that instance of Linux is protected by some sort(s) of malware protection.Actually it is quite likely that Most of the world is interfaced with linux. IN fact you are soaking in it now... (Linux running apache that is )
We interested hobbyists seem to be in good companyI don't disagree with what you are saying here (in both parts).
But just like film, if Linux is going to be viable in the long term for people other than just interested hobbyists, it needs to interface well with the world out there. And the computer world out there is full of those who are at best mischievous, and at worst actively interested in causing mayhem.
And I'd bet a fair amount that that instance of Linux is protected by some sort(s) of malware protection.
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?