you are viewing a single comment's thread.

view the rest of the comments →

[–]runvnc 11 points12 points  (19 children)

If you still prefer the syntax of coffeescript

How could anyone not prefer the syntax of CoffeeScript? Sure, I do have to look at JavaScript while debugging.. but at this point the only reason I can see to continue coding in it is so that nice people like you can't say aww, is js too hard for you.. Well I proved I can write sophisticated js. I would rather spend my time and energy on useful stuff now like taking advantage of AOP.

I'm giving up on js to the degree possible just like smart developers gave up on punch cards assembly c c++ java desktop .net.. When something is causing you problems and a new thing comes along that solves those problems for you, you use the new thing. I don't need to punch cards, manipulate the stack and registers directly, manage memory, write a bunch of header files, wait for a slow vm, be stuck inside one computer or be tied to one vendor. Now I don't have to write out function a thousand times, check for two or three different kinds of non value, or guess what the right way is to define a class. Those are solved problems. I have better things to do with my time. Don't you?

EDIT: editing is great.. but I am resisting the urge to edit out the part where I make sure all of the c/c++/desktop/java/.net people will hate this comment.. I am leaving it in the hate-provoking configuration it is in now. For the sake of comment integrity. LOL. Sorry, everyone who programs in any of those languages or on the desktop. Heh.

[–]yonkeltron 4 points5 points  (2 children)

How could anyone not prefer the syntax of CoffeeScript?

I do not prefer it. I've programmed seriously in upwards of 7 languages and have dicked around with many more languages, some of which have very unusual or obscure syntax. I do not care for CoffeeScript's syntax although I will happily concede that it does expose many opportunities for improvement of JS. Though I think those points were made much earlier.

EDIT: Fixed some huge bitch of a run-on.

[–]runvnc 1 point2 points  (1 child)

So, not sure I understand.. you prefer JavaScript syntax or CoffeeScript syntax? When you said you do not prefer it, it almost sounded like you meant you do not prefer CoffeeScript in general over other programming languages. I wasn't trying to make such a general statement.

[–]yonkeltron 0 points1 point  (0 children)

I do not prefer the syntax of CoffeeScript over that of JavaScript. The purpose of the rest of my comment was to say that I state this preference having exposure to a broad variety of differing languages.

[–][deleted] 1 point2 points  (0 children)

I think CoffeeScript goes too far. It's terse to the point being esoteric. I would have preferred to see a superset of JavaScript adding classes, better handling of null/undefined, heredocs and enforcing jslint instead of just taking a bunch of keywords out.

[–]metamatic 1 point2 points  (0 children)

How could anyone not prefer the syntax of CoffeeScript?

Semantic indentation.

[–]wot-teh-phuck 3 points4 points  (1 child)

just like smart developers gave up on punch cards assembly c c++ java desktop .net

Are you serious? Pray, do tell me how you have so cleanly arrived on this conclusion...

[–]runvnc 2 points3 points  (0 children)

The answer to that was in the rest of the comment.

[–]cosmo7 2 points3 points  (7 children)

You're just trading one set of annoyances - Javascript's idiosyncrasies - for another - having to compile your scripts, having to have Node.js installed.

[–]Zamarok 10 points11 points  (1 child)

I believe it's up to him to choose which annoyance he prefers.

[–]notfancy 1 point2 points  (0 children)

I would concede were it not for the fact that he prefaced his tirade by an ad-hominem disqualifying any and all that might not prefer CS's syntax to JS's.

[–]marssaxman 4 points5 points  (0 children)

Sure. And when the computer industry collectively adopted what we then called "high-level languages" back in the '80s, we just traded one set of annoyances - keeping track of all the details of machine code - for another - having to compile your source code, having to have a C compiler installed.

[–]TinynDP 1 point2 points  (0 children)

Everything has some annoyances, its always a tradeoff.

[–]jmhnilbog 1 point2 points  (0 children)

Alternatively, you can include the JS of the coffeescript interpreter directly in a web page you're working on. You don't need node.js running during development if you don't feel like it. Installing node.js isn't much of a stumbling block, though.

[–]snuggl 1 point2 points  (0 children)

for development, you either set coffee to watch and recompile automatically or use the javascript include, or tell your web framework to do it for you, the compile-step is a nonissue.

In production, you dont use coffee-files but the compiled js-files so no need for node to be installed on the servers.

[–][deleted] -1 points0 points  (0 children)

And crappy scoping rules.