// Dependencies var Cobol = require("cobol");
When .Net came out early 2000s, a Cobol compiler was offered too. There a also numerous way for interoperability from Cobol to Java as well. Both didn’t succeed in cornering and replacing Cobol as far as I know. Maybe Cobol in Nodejs will.
Some things that could help:
- In both .Net and even more in the Java / JVM world there’s a belief that eventually everything has to run in the Virtual Machine, as bytecode, or as .Net intermediate code. Both environments have excellent ways to interoperate with ‘native’ libraries written in C, but that’s less popular. In the Node.js world this quite a common way of working.
While looking browsing at Quora I found this posting by a professor in New Zealand on why certain programming languages are taught at universities while being suboptimal for teaching. Reminds me of this article by Edsger Dijkstra ‘On the cruelty of really teaching computing science’ I had recently read.
A point Dijkstra raises is the problem of explaining by using solely analogies - ‘never refer to parts of programs or pieces of equipment in an anthropomorphic terminology, nor allow your students to do so’.
Avoid using the term ‘bug’, use ‘error’ instead. A bug a fault in software just happens, while an error clearly indicates what it is: wrong code, by fault of the programmer. And ‘programs wanting things, knowing things, expecting things, believing things, etc., and each time that gave rise to avoidable confusions. The analogy that underlies this personification is so shallow that it is not only misleading but also paralyzing.
To wrap up, I’m now sitting in a Seats2meet location in Amersfoort, a place where you can work as freelancer. More quiet then an Internet cafe, but a lot more inspiring then working alone at home. During lunch I met someone who has a youtube channel explaining math - in Dutch. He uses lots of like here:
after all anthropomorphic might be bad, examples are certainly not.
subscribe via RSS