Coffeescript for a production application

[ilya]

Приветствую!

встретил такие ответы:
"We use coffeescript for all of the javascript in BusyConf [http://
busyconf.com/]. A large portion of BusyConf is a client side
application that runs in browers, including support for offline mode.

All of our coffeescript code is fully tested. The tests themselves are
written in coffeescript, and use the Qunit [http://qunitjs.com/]
framework (which is written in javascript). We also wrote an extension
to the Qunit framework that makes the tests nicer. The Qunit extension
is written in CoffeeScript. Our application has a mobile version which
is written in CoffeeScript, and it uses the Sencha Touch [http://
www.sencha.com/products/touch/] framework (which is written in
javascript).

The take away from that is that you can freely intermix javascript
dependencies in your application, but all of the code you write (your
application code, tests, etc) can (and should!) be coffeescript."

Отмечают хороший потенциал использования CoffeeScript на ниве
мобильный приложений (на базе приложений типа http://phonegap.com/) :

"I'd say that most of the production use of CoffeeScript so far is in
conjunction with Appcelerator to create iPhone/Android apps. (Wynn
Netherland of The Changelog blurbed my book by describing CoffeeScript
as "my secret weapon for iOS, Android, and WebOS mobile development"),
but there's going to be a lot more use in production Rails apps--and, I
hope, elsewhere--in the coming months."

Ещё отзыв:
"I really love Coffeescript these days. Essentially the entire
HotelTonight [http://www.hoteltonight.com/] iPhone application is
written in it (using Appcelerator Titanium, which lets you write
"native" apps in JavaScript - they are not web apps, say like
Phonegap). I chose to use Coffeescript in this case because it makes
organizing and maintaining a large amount of JS a lot easier. I also
find it simply a lot more pleasurable to write code with Coffeescript
(vs. JavaScript). We also use Coffeescript for the JS in our Rails
app, but this is incredibly minor/small amount of code in relation to
the entire phone app.

The pros mostly have to do with just being a nicer syntax, but also
that it standardizes an OO mechanism, and then adds some nice
additions (list comprehensions, some scope things, etc.).

The cons are almost zero for me. The primary one is that it's an extra
layer to debug. You will need to look at the generated JS (which is
VERY readable and nice), and then map that to your Coffeescript code.
For us, this hasn't been an issue at all, but YMMV.

In the end, my take is, there is zero risk in terms of using it on a
production app, so, don't let that be a blocker. Then, go try it out.
Write some code with it, compare that to what you'd write in JS, look
at the generated code to see if you are comfy with being able to read
that for debugging needs. Also, hang out in the #coffeescript IRC,
people are good there. And finally, see how it would integrate with
your app, e.g. what's your "build" process (e.g. for Rails, try
Barista, for something standalone, just use the included "coffee -w",
etc.)."




отсюда
http://stackoverflow.com/questions/2954557/has-anyone-used-coffeescript-for-a-production-application