> My context is that I've not looked into TypeScript yet. That means I have no idea how it works. The problem lies in the author, since knowing TypeScript is a

> My context is that I've not looked into TypeScript yet. That means I have no idea how it works. The problem lies in the author, since knowing TypeScript is an essential skill if you are doing anything browser-related or JavaScript-related. Also TypeScript produces readable JavaScript, and anyway it's trivial to mentally strip the types when reading TypeScript, and also very easy to learn enough to fully understand most TypeScript code.