Why CoffeeScript Isn't the Answer
walkercoderanger.com
Why CoffeeScript Isn't the Answer
1–10 of 148 posts
Re: Why CoffeeScript Isn't the Answer
#2This seems to share many of the same things of CoffeeScript I've had. I prefer plain old JS. More readable, unless you're looking at twitter bootstrap code... No semicolons? Such messy code IMO.
Re: Why CoffeeScript Isn't the Answer
#3Coffee-script is awesome but suffers from it's roots as a preprocessed layer on top .. and that essentially leads to poor overall tool chain support .. I actually enjoyed writing code in it .. debugging not so much ..
Would love some of the constructs to make into JS
Re: Why CoffeeScript Isn't the Answer
#4[deleted]
Re: Why CoffeeScript Isn't the Answer
#5Answer to what? What's wrong with Javascript in the first place?
Re: Why CoffeeScript Isn't the Answer
#6I have a rule of thumb that coffeescript is never appropriate for code that has to be require()'d by any code written by somebody else than me.
I'll happily use coffeescript, and enjoy doing so, when that condition is met. It doesn't happen very often though.
Re: Why CoffeeScript Isn't the Answer
#7Answer to what? What's wrong with Javascript in the first place?
He covers that here: http://www.walkercoderanger.com/blog/2014/02/javascript-mine...
Re: Why CoffeeScript Isn't the Answer
#8Answer to what? What's wrong with Javascript in the first place?
For me, coffeescript was the answer to the question "How can I write javascript with python-esque whitespace block formating?" I suspect the author was asking something like "what can replace javascript?"
Re: Why CoffeeScript Isn't the Answer
#9I wonder what the author thinks of GorillaScript [1].
Re: Why CoffeeScript Isn't the Answer
#10[deleted]
"A witty saying proves nothing." - Voltaire