

My memory of it is how unnecessarily arcane it is. I had (and still have) a better understanding of assembly than COBOL. COBOL has hundreds of keywords. And while an instruction set can have thousands of instructions, COBOL still felt more difficult.
Also, nearly any executable can be decompiled to assembly. If you understand assembly, it has a plethora of uses. COBOL can make big bank, but it currently has very limited use.










That could’ve used an example of debugging recursion to show how useful the repl is. I knew about the repl and have used it to find duplicate packages for example, but what it doesn’t help with is finding out how stuff was added to environment.systemPackages and, most importantly, why.
The most glaring omission in nix is the lack of a debugger with conditional breakpoints. Nix is interpreted, is it not? Shouldn’t it be possible to have breakpoints?