[mikey_p]

It just totally fragments the node developer community.

Imagine the confusion when you're working with or contributing to two different libraries that have different indentation or documentation standards. Now make the language different, and mix and match different syntaxes for different languages. Should modules in JS accept patches in coffee? What about vice versa?

Not to mention that coffeescript then becomes an additional dependency, and while in itself that's not bad, I still consider less unnecessary dependencies a positive aspect to a library/framework.

Edit: Why downvoted? Is this not a valid concern?

[jbwyme]

I agree, I would personally prefer it to be pure Javascript.

[paulbjensen]

Hi, this is Paul, I liken the JS/Coffee debate to those wanting to figure out whether to learn Swedish or Danish, the languages are similar, and in fact swedes and danes speak to each other in each other's language, because they're similar.

Disclaimer - I'm still in the pub, What I'm trying to say is, I understand JS, I'm still happy to code in js, but I like teh coffeescript. Let's learn to speak to each other

[mikey_p]

That's why I bring up the fragmentation issue. I actually found coffee to be very pleasant to use, and if it was more standard I would jump head first and never look back at JS, but as it is, I got very frustrated jumping back and forth, and decided to convert all my coffee back to JS (not that it's hard).

To reiterate, I actually love coffeescript, but I see the fragmentation as overall hurting the JS developer community.

[zaxxon99]

well, I speak Norwegian perfectly and close to perfect Danish and Swedish and... I know issues DO happen due to translation (because my Swedish and Danish is only close to perfect ;) ) Will be the same here. Don't get why a startup want this at all.