> They were only trying to use the browser because they had problems with Node (a) not problems with Node, problem. Singular. (the most common and well-documen

> They were only trying to use the browser because they had problems with Node (a) not problems with Node, problem. Singular. (the most common and well-documented problem with Node.) Which they made no attempt to resolve and just gave up on. Immediately. > The fact that there are security issues loading stuff written by the owner of the computer itself from disk is more an artifact of how browsers work and how they evolved than anything else. That was... precisely my point? So... nothing to do with JS. > The usability issue wasn't really with VS Code. It's that the default behavior of browsers Please re-read the gp as this isn't anything related to browsers. It's just a UI feature around display of folders. FWIW Github has the same (quirky, bad) feature in its directory navigation. The "bug" here is that you can't use TypeScript directly in a browser (why not? again, mostly complicated browser related tech politics that no beginner would understand) Oh my. It's not politics it's just age; TS is new. JS is OG. That's all there is to it here. Putting aside any question of whether you might think browsers should adopt TS (agree), even if they did it would still have a different file extension. The bug here is it's Typescript code with a JS file extension. TS is the file extension for Typescript. That's broken code no matter what way you frame it. > He's introduced as "a great computer scientist" Well colour me thoroughly unconvinced.