This is going to be a very interesting poll result. Even 5 or 10% penetration is something remarkable, for a language as widely-used as JavaScript. If you feel like providing any more color beyond your vote, your impressions after using CoffeeScript in anger -- I'd love to hear 'em.
I've never done front end before (I just hate the JS syntax, so I've avoided it, besides a few jsonp requests) but with CoffeeScript I was persuaded to give it a try. Here is my problem. Nothing is Google-able. Even basic things that I get caught up on the answer on IRC is usually "look up how to do it in JS, and then reform it to CS". Maybe I'm starting on the wrong stuff, but even though the syntax is wonderful, ac…
Poll: Have you moved from JavaScript to CoffeeScript?
151–160 of 178 posts
Re: Poll: Have you moved from JavaScript to CoffeeScript?
#152Earlier quoted context omitted.
Browser implementors are working on making easier to debug all compile-to-JS languages, including regular minified JavaScript code. https://bugzilla.mozilla.org/show_bug.cgi?id=618650 https://bugs.webkit.org/show_bug.cgi?id=30933 In the meantime, CoffeeScript tries to make debugging easy by compiling to straightforward, readable JS, with meaningful variable names, normal indentation, and all that. Patches to make the…
Strait forward and readable in many cases but beware: http://jashkenas.github.com/coffee-script/#loops To be clear, I think CoffeeScript is an impressive language/abstraction. I just get tired of people selling the Javascript output as always being "straightforward" and "readable".
Re: Poll: Have you moved from JavaScript to CoffeeScript?
#153Earlier quoted context omitted.
Strait forward and readable in many cases but beware: http://jashkenas.github.com/coffee-script/#loops To be clear, I think CoffeeScript is an impressive language/abstraction. I just get tired of people selling the Javascript output as always being "straightforward" and "readable".
What's wrong with those compiled loops? The only difference from a "hand-written" loop is that you would use `i` and `ln` instead of `_i` and `_len`, and something in context like `numbers` instead of `_results`.
Re: Poll: Have you moved from JavaScript to CoffeeScript?
#154I'm the author of the PragProg book on CoffeeScript: http://pragprog.com/titles/tbcoffee/coffeescript It's heartening to see so many people responding to this poll. I hopped on the CoffeeScript bandwagon more than a year ago; a week of using it was enough to convince me to stop writing pure JS. It's become my favorite language, even overtaking Ruby. (Cue dhh at last month's RailsConf keynote: "Looking at CoffeeScript…
Like most languages at 1.0, though, it has some growing to do. I still find myself needing to dive down into the compiled JavaScript to make sure it's doing what I think it's doing in some unclear situations (nested data structures we used in our tests, for example). I've seldom found a need to take similar actions in more mature languages and I'm sure that will improve as CoffeeScript development continues.
I warmly welcome any tool that makes my life as a developer easier or more enjoyable (CoffeeScript does both) and I hope its success continues to inspire the growth of client-side web development languages.
Re: Poll: Have you moved from JavaScript to CoffeeScript?
#155This is going to be a very interesting poll result. Even 5 or 10% penetration is something remarkable, for a language as widely-used as JavaScript. If you feel like providing any more color beyond your vote, your impressions after using CoffeeScript in anger -- I'd love to hear 'em.
I am strictly a server side programmer and have a problem doing front end work. I want to learn it, but it feels like a sheer cliff to me. The low level CoffeeScript documentation is excellent. What I am looking for and not being a JavaScript programmer this is admittedly difficult for me, is some hand holding on the mechanics. * packaging, how do I import modules or packages? Do these even exist? * debugging, how do…
For details about modules: http://nodejs.org/docs/v0.4.8/api/modules.html
Use the same site for the rest of the API too of course.
I like vows.js for unit testing: http://vowsjs.org/
Re: Poll: Have you moved from JavaScript to CoffeeScript?
#156Earlier quoted context omitted.
What's wrong with those compiled loops? The only difference from a "hand-written" loop is that you would use `i` and `ln` instead of `_i` and `_len`, and something in context like `numbers` instead of `_results`.
There are a total of 9 references to the `_vars`. I think line noise in the compiled javascript is a legitimate counter argument to the claim that its strait forward and readable.
You're also overlooking the fact that this can be considered an advantage: variable naming for these transient uses is very consistent. When writing JS you could have names all over, even a different one for every loop.
Re: Poll: Have you moved from JavaScript to CoffeeScript?
#157Re: Poll: Have you moved from JavaScript to CoffeeScript?
#158Earlier quoted context omitted.
What's wrong with those compiled loops? The only difference from a "hand-written" loop is that you would use `i` and `ln` instead of `_i` and `_len`, and something in context like `numbers` instead of `_results`.
There are a total of 9 references to the `_vars`. I think line noise in the compiled javascript is a legitimate counter argument to the claim that its strait forward and readable.
alert(var one = 2);
In CoffeeScript, (nearly) everything is an expression. So you need to be able to do this: alert one = 2
By pushing up all the var declarations, all assignments can be themselves assigned, returned, or passed as arguments to function calls directly.Re: Poll: Have you moved from JavaScript to CoffeeScript?
#159I think you guys obsess too much about programming languages. I doubt that anybody doing something useful cares about THAT "wohooo expressiveness". JS is alright, dammit. You don't need CS, you need to get your shit done.
Re: Poll: Have you moved from JavaScript to CoffeeScript?
#160Earlier quoted context omitted.
There are a total of 9 references to the `_vars`. I think line noise in the compiled javascript is a legitimate counter argument to the claim that its strait forward and readable.
12 if you count the declaration. You'd have exactly the same doing it yourself, you can at most reduce it to 10 by declaring i and ln inside for(). You're also overlooking the fact that this can be considered an advantage: variable naming for these transient uses is very consistent. When writing JS you could have names all over, even a different one for every loop.
var i, foods = ['toast', 'cheese', 'wine'], foods_length = foods.length;
for (i = 0; i
Prefixing variables with an underscore is not an advantage in readability because it lends nothing to the description of what the variable represents. Its another glyph that you have to visually parse before reaching possible meaning.