For pedagogy reasons, writing something that I would definitely write in #TypeScript in #JavaScript because I can't guarantee the end-user is going to have a TypeScript stack.
JavaScript is still a hole of a language, but I guess I've used it long enough that I'm getting that Cypher-in-the-Matrix thing.
"I don't even see the lack of modules. I just see closure, closure, one exposed variable name..."
@mattock Same. I have some students who are just getting started in JS and I don't want to hit them with modules (or my personal professional opinion of "Never use this language and just use TypeScript" ;) ) out of the starting gate.
... although one issue with bare JS is, unfortunately, that when done right (i.e. to hide symbols and create something like modules without modules) it looks goofy.
