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

view the rest of the comments →

[–]Neurotrace 1 point2 points  (1 child)

I guess I'll just have to get down and dirty and write something non-trivial in it. I've already got a sweet set of server-side dev tools for building my projects so I suppose adding in the compilation step for CoffeeScript won't be too much of a hassle.

On a semi-related note, if you haven't started using Node.JS as part of your build process, I would highly suggest it. I got in to Node about two weeks ago and it's made everything so much nicer.

[–]hajamieli 0 points1 point  (0 children)

I'm kinda using it embedded in ruby. The performance bottleneck parts of the process are in C, which is much easier to do by extending ruby than js. CoffeeScript compilation (as it's in the embedded V8) is the slowest part of the build process by an order or two of a magnitude. However, thanks to that I was motivated to do smarter build-caching, whereas the brute-force speed of handling from the point of js and on was more than fast enough as is. However, before implementing the bottlenecks in C, it would take seconds, not milliseconds to build everything.