IssueRaiser

The problem I have with "output to Javascript" languages is that debugging becomes hell.

The problem I have with "output to Javascript" languages is that debugging becomes hell. Line numbers no longer correspond to each other, for example. A slightly less-hellish but still annoying problem is that I often poke at things directly from the console when bugs happen, and this helps me a lot in debugging. However poking at the console requires using JavaScript, which is fine, but it would drive me nuts to have to code in one language (e.g. CoffeeScript, TypeScript, Python) and debug in another (JavaScript) and switch my brain back and forth every few minutes. So I've ended up largely sticking with writing code directly in JavaScript. Any good solutions to this? Are there replacements to the Chrome JavaScript console that supports those other languages?

Posted by dheera on May 6, 2015, 2:39 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.6,500 issues0 comments

hackernews (Other)

The problem I have with "output to Javascript" languages is that debugging becomes hell.

dheeraMay 6, 2015, 2:39 PM

The problem I have with "output to Javascript" languages is that debugging becomes hell. Line numbers no longer correspond to each other, for example. A slightly less-hellish but still annoying problem is that I often poke at things directly from the console when bugs happen, and this helps me a lot in debugging. However poking at the console requires using JavaScript, which is fine, but it would drive me nuts to have to code in one language (e.g. CoffeeScript, TypeScript, Python) and debug in another (JavaScript) and switch my brain back and forth every few minutes. So I've ended up largely sticking with writing code directly in JavaScript. Any good solutions to this? Are there replacements to the Chrome JavaScript console that supports those other languages?

Comments (0)

No comments yet. Start the discussion.

Comment on this issue