I was looking into learning COBOL some years ago, because i found that verbosity interesting.
And it seemed like there’s not many libs and toolboxes out there, compared to the major languages that has libs for everything, so I couldn’t really use it for small projects.
The issue with COBOL surely isn‘t about the language itself. The real challenge will be to decipher the spaghetti code that was created at a company in the last sixty or so years. And then to dare changing something without breaking the program as a whole.
I was looking into learning COBOL some years ago, because i found that verbosity interesting.
And it seemed like there’s not many libs and toolboxes out there, compared to the major languages that has libs for everything, so I couldn’t really use it for small projects.
The issue with COBOL surely isn‘t about the language itself. The real challenge will be to decipher the spaghetti code that was created at a company in the last sixty or so years. And then to dare changing something without breaking the program as a whole.
That’s easy you just use the huge number of test cases to ensure against introducing new bugs.
/S