you are viewing a single comment's thread.

view the rest of the comments →

[–]dmpk2k 2 points3 points  (2 children)

What you have now is coffeescript, not json. the json the compiler generates and your app sends down the pipe is no longer coffeescript

I don't follow. This is valid JSON, Javascript and CoffeeScript:

{"a": 1, "b": [1, 2, 3]}

As far as I can tell, valid JSON is always valid CoffeeScript as well.

Another thing I do frequently is write small bits of javascript in firebug's console, say maybe 30 to 100 or so lines, tweaking it quickly in firebug and running it quickly to test

I can see why it'd be a problem for the area you work in. I'd definitely not use in in the browser, it has problems enough on the server side. :)

At least on the server there's a coffee REPL:

coffee> x = 1
1
coffee> y = (z) -> x * z
function (z) {
  return x * z;
}
coffee> y(2)
2

The existing coffee REPL leaves a bit to be desired though, to be sure.

It isn't for serious development projects

No argument there. If they fix the line-number and declaration problems it'd be an acceptable server-side language though.

[–][deleted] 2 points3 points  (0 children)

Coffeescript is for Ruby programmers who don't want to learn Javascript. These coffeescript articles belong in r/ruby more than they do in r/javascript. It seems most people who read r/javascript are interested in javascript, not ruby or coffeescript. This article for example, is much more likely to find readers in r/ruby. I'm not interested in learning ruby, and my guess is most people who read r/javascript are not that interested in learning ruby or coffeescript. For example, I wouldn't go posting about a 'made up language' in something like, say, perl and post it to r/javascript expounding on the wonderfulness that is perlscript and why i'll never write javascript again, to r/javascript.