131–140 of 178 posts
I 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.
Alright, I buy your argument. Now go and do everything in assembler, right now. Deadline is yesterday. What are you looking at?? Go!!!
Is it only me who likes JS better than CS? :( It's stylish.
I started writing some of my code in coffeescript a while ago, but then I started a coffeescript project that grew into a file of 2000 lines and it became very hard to skim the code and gather meaning from it because of the lack of parenthesis and the indentation-based nature of it.
Earlier quoted context omitted.
Well, you do choose Javascript when you could have chosen PHP and had even more overlap. Presumably, because you believe it is better for the tasks. Similarly, Coffeescript authors believe that Coffeescript is better than Javascript -- even if there's less overlap.
Will understanding the CoffeeScript syntax help me learn another programming language like JavaScript did?
Guess which is more valuable :)
Earlier quoted context omitted.
I use coffeescript both clientside and serverside (node). Since semantically the coffeescript maps to javascript almost one-to-one, the only debugging difficulty is mapping line numbers in the error output to the location in the coffee file. Client-side is zero problem because the chrome and firebug developer tools jump you right to the line in the JS file, and you can figure out where the error is there since the co…
Have you tried using node-inspector for server-side code debugging? https://github.com/dannycoates/node-inspector
Earlier quoted context omitted.
You may have been misinformed -- the values of direct, raw, fast code are a big part of the reason why CoffeeScript works the way it does, and why many scripts can end up running faster after getting ported to CoffeeScript. The golden rule of CoffeeScript is to avoid adding any library code to the runtime, and to avoid introducing any special calls, to the greatest extent possible. Many folks rely on a "forEach" (or…
I'd write that snippet the following way: for (var i = 0, ii = list.length; i Or: for (var i = 0, ii = list.length; i There are ways to make normal JavaScript not look ugly ;) EDIT: fixed minor oversight
for i in [0...list.length] by 1
sum += list[i].amount
I've used C and Java since high school, but I'm happy to be rid of that old `for` syntax. And I love that curly braces means only one thing in CoffeeScript: "I'm defining a new object with these key-value pairs."
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 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…
* in firebug / web inspector
* qunit, jasmine etc
repl for node
### REPL ###
repl = require 'repl'
r = repl.start 'REPL> '
r.context.client = -> exec("open http://localhost:# {config.port}/") ; return