COBOL in 100 seconds
Video Statistics and Information
Channel: Fireship
Views: 774,468
Rating: undefined out of 5
Keywords: cobol, cobol language, programming, cobol basics, parody, compsci, computer science, mainframe, ibm, mainframe computer, 100secondsofcode
Id: 7d7-etf-wNI
Channel Id: undefined
Length: 2min 3sec (123 seconds)
Published: Sat Apr 11 2020
Please note that this website is currently a work in progress! Lots of interesting data and statistics to come.
βSo itβs responsive on mobile devicesβ haha. That or the syntax error is my favorite part.
/Console spitting errors/
"600 Reserved words for you to memorize..."
That's a hell of an entry barrier. When you look at more common languages like Java or python, they expand into their own form of monstrosity with libraries and objects. But an explosion of libraries seems easier to digest than having a huge dictionary to deal with because it's built on a simple foundation. I.e. a few keywords built around "everything is an object."
This kinda seems like a parallel of 26 english characters vs hundreds/thousands of glyphs in some asian languages.
For those with experience, can you guys chime in. Are these keywords substantial or is a lot of it something you would not use the majority of the time?
I was disappointed to find other videos in this series are somewhat serious. This is a great format to roast any aspect of engineering.
That Dilbert episode sort of predicted the current COBOL drama: https://www.dailymotion.com/video/x2fhokx (at 16:10)
The only thing funny in there was a six-figure salary for COBOL programmers. Where? I'm available.
Program not compiling because you didn't align the columns correctly was fun. Also English words for everything but if you want to declare a structure, well that keyword is 888 of course.
βIt was developed over 100 hundred years ago in 1959β
What year are we in?
Flashbacks
COBOL is easy to write, difficult to make right
The "data structures" are hierarchical, just like management
Just don't mix up, grandparent, parent & child when processing files
And whatever you do, don't paste a program into the middle of itself (using VIM this is easy to do by being in the wrong mode) the compiler gets Trump level confused