3 ms·
> TypeScript doesn’t absolve you from learning JavaScript. When things go awry, you’ve still got to be able to spelunk the JavaScript code it produces. I've wr
by arcticfox 8y ago
> TypeScript doesn’t absolve you from learning JavaScript. When things go awry, you’ve still got to be able to spelunk the JavaScript code it produces.
I've written several projects in Typescript and I don't think I've ever had to analyze the transpiled code. I'm curious how esoteric the situations are where this is still necessary.
- sonnyblarney 8y agoConcur. I'm always checking underneath the hood 'because' ... but I have not actually come across a case wherein I've had to. That said - I think the comment is valid. Transpiling is not compiling and we have not choice but to remain vigilant on the JS, of course, it's not that hard, especially with ES6.
- foobiekr 8y agoCode has bugs. I don’t even write that much typescript and I’ve looked trough the transpiled code just so that when I encounter a bug I’ll be familiar enough to debug through that layer.
- edoloughlin 8y agoI've been using Typescript for three years, both in the browser and in NodeJS. The only time I've seen JS in my debugger is when source maps weren't configured/found. I've never had to fall back to JS for debugging.