4 ms·
The hatred comes from people like me, who have worked with COBOL and will tell you it's terribly frustrating to work with, needlessly verbose in multiple places
by the_af 6y ago
The hatred comes from people like me, who have worked with COBOL and will tell you it's terribly frustrating to work with, needlessly verbose in multiple places where it doesn't need to be, and often used in banks for purposes which are the death of all you hold dear or interesting to work with.
COBOL is not an interesting programming language these days, and you should not learn it unless you need it for your current job.
> [COBOL was] designed, initially, for non-programmers to be able to describe in words what it is they would like to accomplish in a way they could be understood by the computer.
Let me tell you a secret. It doesn't work for non-programmers. The complexity of "Z = X + Y" is no more or less than "ADD X TO Y GIVING Z", and bugs will happen at the same rate with either syntax. The added verbosity will only annoy you.
Another myth surrounding COBOL is that as its programmers age, there is a lack of them and therefore COBOL jobs are high-paying and you should learn it to make good money. The reality: I've never met a really wealthy COBOL programmer -- or rather, one who was wealthy because he/she knew COBOL. That's not where the money is. COBOL jobs are not particularly well-paying, and there are young people learning it, and no, they don't get awesome paychecks.
- carlmr 6y ago>Let me tell you a secret. It doesn't work for non-programmers. The complexity of "Z = X + Y" is no more or less than "ADD X TO Y GIVING Z", and bugs will happen at the same rate with either syntax. The added verbosity will only annoy you. Not to mention that verbosity often distracts from meaning, leading to more place for bugs to hide.
- monoideism 6y ago> COBOL jobs are not particularly well-paying, and there are young people learning it, and no, they don't get awesome paychecks. But say this to non-programmers, and they vehemently deny it's true. And always cite a friend of their neighbor who made it good from COBOL. It's like they need to believe there's a shortcut out there to sure wealth as long as you're smart and work hard.
- kps 6y ago> It doesn't work for non-programmers. It wasn't designed to work, it was designed to please senior management. Grace Hopper: “I used to be a mathematics professor. At that time I found there were a certain number of students who could not learn mathematics. I then was charged with the job of making it easy for businessmen to use our computers. I found it was not a question of whether they could learn mathematics or not, but whether they would. […] They said, ‘Throw those symbols out — I do not know what they mean, I have not time to learn symbols.’ I suggest a reply to those who would like data processing people to use mathematical symbols that they make the first attempt to teach those symbols to vice-presidents or a colonel or admiral. I assure you that I tried it.”
- Viliam1234 6y ago> Throw those symbols out — I do not know what they mean, I have not time to learn symbols. Wouldn't it be easier to just use C/C++, and define macros like "PLUS" that explands to "+", "MINUS" that expands to "-", "BECOMES" that expands to "=", etc.? Oops, COBOL predates C. :(
- galoisgirl 6y ago> COBOL jobs are not particularly well-paying, and there are young people learning it, and no, they don't get awesome paychecks. Yup. All the articles on the shortage of COBOL programmers is actually companies whining that they can't find cheap labor. If they paid well, they'd have their pick of young and old.
- rhabarba 6y agoWell, if they paid for COBOL courses, that is. COBOL still evolves.
- emidln 6y agoIf they paid well enough, your average working programmer would flip to COBOL for a pay raise. Once you've learned a few languages, you can solve problems in any language. It's just about having the manual and maybe an overview of available facilities so you don't have to read all the docs upfront. The syntax doesn't matter for data plumbing applications. COBOL is as good as BASIC as good as Java as good as Python etc. You might prefer writing Python (or Haskell, Clojure, Rust, C++, Go, Scala, Kotlin, whatever is en-vogue these days) because it is more concise, but if you can effectively hack in one language you can do it in COBOL too with a little effort.
- pbourke 6y agoIt’s not the language but the ecosystem that’s a barrier to entry. Do you have a z series in your garage to hack around with?
- galoisgirl 6y agoI have 3 free accounts on Mainframes from various courses to hack around with. I looked at jobs in my area and some don't require any experience, they train you. There's also the kid who just bought a Mainframe: https://www.fastcompany.com/3063265/this-teenage-ibm-employee-got-his-job-by-buying-an-old-mai https://www.fastcompany.com/3063265/this-teenage-ibm-employe...
- goatinaboat 6y agoThe reality: I've never met a really wealthy COBOL programmer -- or rather, one who was wealthy because he/she knew COBOL. The pay is at the intersection of "knows COBOL" and "knows the problem domain inside out". The problem domains are not something most people would ever have been exposed to without getting in in the first place as COBOL programmers.
- the_af 6y agoI don't disagree with you. But note most people learning COBOL won't get those high-paying jobs; they'll instead end up maintaining legacy and boring corporate systems. And COBOL isn't a particularly interesting language to learn: in the spectrum between boring <--> cutting edge, COBOL lands on the far side of "very boring"!