Comment on: AI migrated legacy COBOL programs to Java, bugs included
I remember a similar story shared this year at JAX2026 from the Sparkasse Group, they said they were using AI to migrate from COBOL, but they still were in the middle of the migration. Maybe they faced the same issues / problems? It seemed pretty zealous to me, that everything was working smoothly, but this article highlights the limitations
Comment on: AI migrated legacy COBOL programs to Java, bugs included
Yes, and it's a surprising good part about PHP (a language that otherwise has an enormous collection of warts, to put it mildly).I feel like the more dynamic and/or weakly-typed the language is, the more important it is to have a separate concat operator.The worst ones being weakly-typed and dynamic. Consider `'5' + '10'` in JavaScript vs `'5' - '10'`.
I also very much dislike Python's `+` for concat, but at least it's more strongly typed.PHP, Lua, and Erlang are three examples of dynamically-typed languages with separate concat operators (`.`, `..`, `++`; respectively), and they all are bette
Comment on: AI migrated legacy COBOL programs to Java, bugs included
As someone that has worked at a bank maintaining RPG/COBOL and Java, the latter definitely encourages programmers to wrap things in yet another class. They think they're simplifying, but in reality, they're piling abstraction layers that have to be peeled off one by one when, for example, you're tring to find that EBCDIC-to-UTF8 bug.A good Java architecture is possible, though, but it requires planning, discipline, and restraint; and yet the ever-changing business needs can mar your beautiful building given enough time. COBOL is simpler and more straightforward, you have to go out of your way