News for hackers. Stuff that matters.
Re:TypeScript 4.1 by Vinnl on Friday November 20, 2020 @03:24PM (#25164539)
> caught by JS runtime

This is a major point: "caught by JS runtime" means you're only able to see it when you actually run your application and exercise that code path - or worse, that your user does so. Where the alternative is your editor literally indicating the error the moment you write it, the fix costing you so little time that you can fix them practically subconsciously.

Re:TypeScript 4.1 by hajile on Friday November 20, 2020 @07:22PM (#25166756)
Catching syntax errors is the realm of linters, but if you don't have a linter, the parse phase will immediately tell you that you messed up.
Re:TypeScript 4.1 by Vinnl on Saturday November 21, 2020 @06:57AM (#25169205)
That's interesting, cause you mentioned the JS runtime earlier. In any case, unless you'd argue that you never get a single runtime error, I'd encourage you to take a moment every time you encounter one whether that could have been caught by TypeScript. In my experience, that is the case more often than you might think.