The pains of forced cobol.

Cobol Sucks

Its nearly the end of 2006 and I'm so close to finally graduating with my B. A. I can taste it. Only two more classes to go! A business analysis class and.... cobol. Why am I taking a cobol class? You're right...it is 2006, and .Net has all but taken over. But I'm a Computer Information Systems major at MTSU, and I must take it to graduate.

So now I'm going to bitch and moan. Well, I'll do better than that. I'll show you why I think cobol sucks so badly. Listed below are two files related to our first assignment. The first file is the actual code. The second file is the output generated by the program.

Click here for the program's code.

Click here for the program's output.

"Millions of lines of code are written in Cobol every year." Obviously. If you want anything done at all in cobol you can expect to write 100 lines of perfectly line-positioned code. Outside of cobol being obsolete, that's my biggest complaint.

I'm through bitching.

(by the way, if you're suffering through a cobol class, feel free to use that code for what ever. I don't care one bit.)