5 ms·
Do any of these languages solve the debugging problem? I'd love to write my client-side code in something other than JS, but I'd still be debugging it in JS, a
by nickzoic 14y ago
Do any of these languages solve the debugging problem?
I'd love to write my client-side code in something other than JS, but I'd still be debugging it in JS, and I have trouble believing that's going to help ...
- iso-8859-1 14y agoThat's what Source Maps are for. Currently supported in a superset of {CoffeeScript, TypeScript and GWT}.
- pjmlp 14y agoSadly very few browsers support them.
- detst 14y agoDart. You debug in Dart and it's (generally) considered a bug if the generated JS deviates in behavior. The JS is rather readable, if needed. It also runs server-side.
- nickzoic 14y agoThanks! (and the other guys too, but Dart seems most like what I was looking for ...)
- kevingadd 14y agoMany of the compilers generate relatively human-readable output JS, so if you know JS, you can debug the output. This is still true for JSIL (albeit less than before... sigh) and is obviously true for languages like TypeScript where the mapping is direct.
- 1bo1bo1 14y agoGo2js (https://github.com/kless/go2js https://github.com/kless/go2js). Translator from Go which was designed to translate line-to-line, but you should debug on Go since it's much easier.