News for hackers. Stuff that matters.
Re:AI migrated legacy COBOL programs to Java, bugs included by someone654 on Monday August 03, 2026 @04:20AM (#49152764)
> Now, no one does.

I got a chuckle over this, but in my experience working on legacy systems, this is the case already. Using AI to translate/explain the code brings extra understanding.

Re:AI migrated legacy COBOL programs to Java, bugs included by m4rtink on Monday August 03, 2026 @06:50AM (#49153995)
Can it really explain the code if the information is not there anymore ? It was in a binder that got shredded 40 years ago by accident.

More like it will hallucinate some explanation & cause even more confusion.

Re:AI migrated legacy COBOL programs to Java, bugs included by free_bip on Monday August 03, 2026 @10:08AM (#49156000)
If what you want is the "Why", you're right it probably won't get it right. It'll just give you baseless speculation. But if what you want is the "What" or the "How", I think it can be useful.
Re:AI migrated legacy COBOL programs to Java, bugs included by sharts on Monday August 03, 2026 @08:01PM (#49162904)
The code is the information. If you need binders of info then it wasn’t codified
Re:AI migrated legacy COBOL programs to Java, bugs included by pixel_popping on Thursday August 06, 2026 @09:42AM (#49196579)
Yes, it would take a long time for humans to remake a documentation from the codebase itself, but AI could do that much quicker and with close to perfect accuracy, Code is superior to documentation as it's the direct intended behavior (including bugs), in a sense, we won't even need documentation in the future, except maybe to lower AI costs.
Re:AI migrated legacy COBOL programs to Java, bugs included by Zenst on Monday August 03, 2026 @04:38AM (#49152902)
Whilst true, it's not without its gotchas, and I saw a video the other day that elegantly highlights this: https://www.youtube.com/watch?v=t6MAZW-joCo. A false sense of confidence is bad; one that is offloaded onto somebody else is another.