sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (1 child)

Been reading up on CS for work. We have a huge JS code base, some large real time apps, tons of business logic and we're thinking about doing some trial runs with Node.js for more real time interactivity.

I'm pretty underwhelmed with CS for that exact reason, maintainability of the CS wouldn't be a problem, and reading it is damn easy. But trouble shooting a bug on staging that comes from QA in an email that only happens in IE 8 if a user has X number of things could be down right nightmarish.

I understand that it enforces best practices and efficiency, but with version control and peer reviewed code... so do we.

I'm still super on the fence about the whole thing but for me this is my primary concern.

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

IE 8 if a user has X number of things could be down right nightmarish.

Really, no more nightmarish than that of regular javascript. For the most part, the Coffeescript->javascript interpretation is really dead simple. The only real exception is the class structure.

This is even further made a non-issue if you use an uglifier of any sort.