2 ms·
> For better or worse a lot of COBOL code also gets replaced when new compliance measures like Basel II and III are implemented. That's really not my experienc
by shakna 9y ago
> For better or worse a lot of COBOL code also gets replaced when new compliance measures like Basel II and III are implemented.
That's really not my experience.
I was brought in to maintain, and manage a series of changes to a major bank in Australia, where I trained a full-time replacement before leaving.
We replaced COBOL code... With more COBOL.
> Additionally, there are even transpiler-like tools that convert COBOL to Java code. The resulting code of course is horrible but at least it then is available in a language with a long-term maintenance outlook.
Not just horrible to look at. Slow. Performance that is hundreds to thousands of times slower than the pre-existing code. That's just not acceptable.
---
Now, we were writing "new" stuff in a different language - C++, because IBM has a wonderful linker framework between Fortran and C++ on their mainframes. But the COBOL is staying put, because nothing can really replace it without unacceptable downtime or performance regressions.