3 ms·
I think that the "beauty" (if you want to call it that) of COBOL was mostly in how it did, for the most part, exactly what you told it to do and rarely surprise
by commandlinefan 9y ago
I think that the "beauty" (if you want to call it that) of COBOL was mostly in how it did, for the most part, exactly what you told it to do and rarely surprised you with unintended consequences (I mean, don't get me wrong, it still did, but not like C or Java or Javascript do). The problem was that you gave up a lot of expressiveness for this; when I was working in COBOL, I'd find myself cutting and pasting the same snippet of code in dozens of places with minor modifications - the language just didn't allow enough dynamism to permit decent code reuse. So in exchange for making it harder to accidentally shoot yourself in the foot, you'd end up with a codebase that needed dozens of code changes, far distributed from each other, to make functional updates - and hope that you didn't forget to update one of the cases.