3 ms·
They’d have to be revalidated. Don’t fix it if it’s not broken. Edit: and when do you upgrade? If they upgraded in ‘85, it would be in C++. ‘95, and it would b
by jimbob45 7y ago
They’d have to be revalidated. Don’t fix it if it’s not broken.
Edit: and when do you upgrade? If they upgraded in ‘85, it would be in C++. ‘95, and it would be Java 1.0. ‘05 and it would have been VB6. None of those would have been substantially better save that they would have been easier to hire maintenance programmers for.
- luckylion 7y agoAnd now that they're broken, they can't be fixed. ;) With so many legacy systems that are often in very important places, I wonder whether it wouldn't be smarter to spend money on systems converting a modern language to cobol, e.g. python2cobol. Is that impossible?
- number6 7y agoI guess there are technical reasons. a big bank does risk assessment. I can't imagine a problem like this will go unnoticed for long
- number6 7y agoOk got it. But it seems to be broken somehow if they need programmers now. Maybe write the tests first so it can be validated easier?
- ghayes 7y agoC++ or Java seem like great alternatives. And I don't get the reference to VB6-- in 2005, it would still have been Java, and in 2015.
- bluedino 7y agoUpgrade? You mean re-write.
- tossup8536 7y agoJava 1 could actually be progressively migrated to up to date java 11. It would have been a fantastic choice if they had started a reimplantation. (Unless performance was an issue)