It was an extremely, easy-to-use language that even laypeople could write business logic in. Similar to how BASIC got so many people started. Except, Fortune 500 companies were writing all their backend stuff in COBOL on mainframes from the 60&#x27;s onward. Needless to say, there&#x27;s a <i>lot</i> of it around dependent on existing libraries, interfaces, language variants, compilers, etc. Porting it is huge risk. So, they just maintain and extend it.<p>Main vendor even has it on Visual Studio:
<a href="http:&#x2F;&#x2F;www.microfocus.com&#x2F;solutions&#x2F;cobol&#x2F;index.aspx" rel="nofollow">http:&#x2F;&#x2F;www.microfocus.com&#x2F;solutions&#x2F;cobol&#x2F;index.aspx</a><p>The job is boring, predictable, and 9-5-ish at most places. Exactly what some types of people are looking for. They figure they can play with the fun stuff at home. One person even jokingly made a web framework for it: COBOL on Cogs. So, yeah, I throw COBOL at anyone using the &quot;use language X for users or jobs&quot; argument to see how they react to what they&#x27;re actually arguing.<p>Interesting that you at least looked it up and didn&#x27;t go into denial mode. I&#x27;m impressed. ;)