Cesar R M
Well-Known Member
I think you misread what I said. I said, do you spend money to upgrade it IF it's working as designed? So no, I'm not suggesting it be re-written in whatever the new trending thing is. I said if it works you do NOT change it. I also said the last thing you do is say let's re-write or overhaul it because it's been a while. It adds unnecessary risk and cost
You might want to re-read what I said before getting on your high-horse. By "language of the week" I guess you mean JAVA which is almost 20 years old.
Except Java was never designed nor works for such critical implementations? the strength of java is its portability. It can be slow, clunky and unreliable.. but WORKS.
critical systems needs efficiency and primarily.. stability.
the only thing that would have made them be forced to upgrade.. would be the incompatibility of the intercommunication.
If you have a system that as always been programmed and designed to be standalone, it wont be playing well if you try to cram it to an unified system.
Kinda like trying to link an active system with tons of clients.. to an old ancient database that only could handle 1 transaction per turn(and not like now, where you can have thousands or millions of concurrent ones)