Live data from Hacker News

Intro to CoffeeScript

aseemk.com

91–95 of 95 posts

Re: Intro to CoffeeScript

#91
post #47
post #27

I mostly enjoyed the slides, and I'm interested in CoffeeScript, especially since I'm going to be working a little in Node in the near future. This post is a critique on the blog post, rather than on the slide content, which was more or less fine. Too much focus placed on how those who dislike it haven't given it a proper shot. This could be true, but six paragraphs is overkill. You make a few points: A) they aren't…

Sounds like the OP has to justify his large mental investment he made in CS by bashing others who have different opinions. "I'm not a blub like them. I'm not close-minded like them. I'm not doing mundane things like them." It's a telling sign about a language when the language advocates have to employed negative psychological ploys to convince people (or convince themselves) to use the language.

On the contrary, it seems that OP was going out of his way to explain that it's acceptable to have initially hated CS.

If CS is actually terrible, why don't we talk about what actually makes it terrible? I can't comprehend the notion that evaluating the advocates of X will demonstrate anything concrete about X.

Re: Intro to CoffeeScript

#92

Earlier quoted context omitted.

The overhead of having an additional dependency. The more moving parts there are, the more things can break.

Then why don't you write assembly?

Because high level languages provide me a significant freedom from concerns about implmentation, freeing up my mental cycles for the business problem at hand.

The height of the level of js and cs don't seem significantly different.

Re: Intro to CoffeeScript

#93

Earlier quoted context omitted.

After you load up the CoffeeScript module in your app.js (server.js etc) you can actually write an entire node.js app in CoffeeScript.

(Or just run the .coffee with "coffee" instead of "node")

True, I was thinking about universal deployment to PaaSes, etc

Re: Intro to CoffeeScript

#94

My biggest issue is that the language can be ambiguous and I'm not sure how to check what I'm compiling to without running the short cut all the time in Sublime Text 2

the coffee console app has a watch parameter iirc.. as do many build tools...

I'm not worried about the actual build step. I'm talking about that sometimes it's hard to figure out how the CoffeeScript compiler is parsing and generating the JavaScript

Re: Intro to CoffeeScript

#95
post #86
post #25

> What I find sad, though, is that most people who dislike CoffeeScript don’t truly know it. They haven’t taken the time to really learn it, or even try it. Their reactions are usually knee-jerk, or based on fallacies. [...] The explanation for most people’s dislike of CoffeeScript is probably our natural resistance to new things and our comfort in what we know. Oh, wow. I've been using CoffeeScript for about a year…

> The ecosystem is weak not to say non-existent comparing to JS In what circumstance is it appropriate to consider the CoffeeScript ecosystem to be distinct from the JavaScript ecosystem? > [...] and every JS solution and example out there It seems impractical to regularly code in CoffeeScript without being fluent in JavaScript. FWIW I agree with you about CoffeeScript being a little finicky about the syntax. There's…

> In what circumstance is it appropriate to consider the CoffeeScript ecosystem to be distinct from the JavaScript ecosystem?

Example code, debugging tools, message forums, developer teams.

Post reply on HN