3 ms·
> 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
by Vinnl 6y ago
> 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.
- hajile 6y agoCatching 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.
- Vinnl 6y agoThat'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.