3 ms·

Go ahead and [do this horrible thing], it's not _that_ bad. > especially given the still-crude state of JavaScript debugging tools in general I feel like peop

Go ahead and [do this horrible thing], it's not _that_ bad. > especially given the still-crude state of JavaScript debugging tools in general I feel like people don't know how to use web inspector... There will never be native CoffeeScript, you will always debug the JavaScript.

jjm 15y ago
"There will never be native CoffeeScript" Sure, but we'll learn from CoffeeScript and apply it to the next ECMA ver. The CoffeeScript discussion is a worthy one, but declaring it unworthy to have a seat at said table prevents progress. I'd rather read articles on how to make things better instead of bashing.
chc 15y ago
> Go ahead and [do this horrible thing], it's not _that_ bad. Sure. Let me insert a few things that can have really bad side effects that I still think you should do: • Leave your house every day (car crashes ROFLstomp homicide as a cause of death) • Eat food (most foods have some ill effect on your body) • Write some code in C (it's a very unsafe language, but sometimes necessary) • Use a computer (hurts your eyes and causes carpal tunnel syndrome) Long story short, everything looks horrible if you only look at the bad parts of things. > I feel like people don't know how to use web inspector... You're right, many people don't. I'm not one of them, but I encounter them all the time. That kind of thing is still relatively new, so it's hard to blame them as much as pity them. And of course the Web inspector isn't there outside of a Web browser context. > There will never be native CoffeeScript, you will always debug the JavaScript. I never said there would be native CoffeeScript; I meant they will support source maps for alternative languages. Unless the CoffeeScript compiler is introducing bugs into correct code, being able to get error line numbers in your CoffeeScript file will mean that you mostly won't have to debug the generated JavaScript.
- ryanflorence 15y ago
  Source maps will be helpful, but I still can't put a break point in my coffee script from the browser.
  - jeswin 15y ago
    Assuming the coffee script files are accessible over a url, wouldn't that be possible with a Firebug extension? Which basically maps the break point to JS.
mambodog 15y ago
I dunno, it would seem that upcoming SMAP support in Firefox and Webkit[1] comes pretty close to debugging the CoffeeScript directly. [1] http://www.infoq.com/news/2011/08/debug-languages-on-javascript-vm http://www.infoq.com/news/2011/08/debug-languages-on-javascr...

jjm 15y ago

"There will never be native CoffeeScript" Sure, but we'll learn from CoffeeScript and apply it to the next ECMA ver. The CoffeeScript discussion is a worthy one, but declaring it unworthy to have a seat at said table prevents progress. I'd rather read articles on how to make things better instead of bashing.

chc 15y ago

> Go ahead and [do this horrible thing], it's not _that_ bad. Sure. Let me insert a few things that can have really bad side effects that I still think you should do: • Leave your house every day (car crashes ROFLstomp homicide as a cause of death) • Eat food (most foods have some ill effect on your body) • Write some code in C (it's a very unsafe language, but sometimes necessary) • Use a computer (hurts your eyes and causes carpal tunnel syndrome) Long story short, everything looks horrible if you only look at the bad parts of things. > I feel like people don't know how to use web inspector... You're right, many people don't. I'm not one of them, but I encounter them all the time. That kind of thing is still relatively new, so it's hard to blame them as much as pity them. And of course the Web inspector isn't there outside of a Web browser context. > There will never be native CoffeeScript, you will always debug the JavaScript. I never said there would be native CoffeeScript; I meant they will support source maps for alternative languages. Unless the CoffeeScript compiler is introducing bugs into correct code, being able to get error line numbers in your CoffeeScript file will mean that you mostly won't have to debug the generated JavaScript.

ryanflorence 15y ago
Source maps will be helpful, but I still can't put a break point in my coffee script from the browser.
- jeswin 15y ago
  Assuming the coffee script files are accessible over a url, wouldn't that be possible with a Firebug extension? Which basically maps the break point to JS.

mambodog 15y ago

I dunno, it would seem that upcoming SMAP support in Firefox and Webkit[1] comes pretty close to debugging the CoffeeScript directly. [1] http://www.infoq.com/news/2011/08/debug-languages-on-javascript-vm http://www.infoq.com/news/2011/08/debug-languages-on-javascr...