# Is it better for Discourse to use JavaScript or CoffeeScript?

**URL:** <https://meta.discourse.org/t/is-it-better-for-discourse-to-use-javascript-or-coffeescript/3153>\
**Category:** Development\
**Created:** [February 15, 2013, 1:34pm UTC](https://meta.discourse.org/t/is-it-better-for-discourse-to-use-javascript-or-coffeescript/3153 "2013-02-15T13:34:20Z")\
**Posts on this page:** 1\
**Showing post:** 22

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [February 16, 2013, 1:07am UTC](https://meta.discourse.org/t/is-it-better-for-discourse-to-use-javascript-or-coffeescript/3153/22 "2013-02-16T01:07:07Z")

</div>

> [@eviltrout](#):
>
> hybrid of Ruby/C because gems we use have FFI

I guess, but less of a hybrid, if every single time I debugged Ruby I had to run GDB and constantly found myself reading C source I think it would be closer. If every time I wrote I line of Ruby I had to construct a mental model of the way MRI is going to translate the thing to C (for example because I need to know its going to wrap up my switch statements in a closure or what have you), we would be a more of a hybrid system.

> [@danneu](#):
>
> that it ostensibly outweighs the benefits that non-hypothetical, real-life Discourse contributors experience while maintaining a Coffeescript codebase

Well, we have seen almost no contributions from the community wrt refactoring our js and we are a HUGE js app. In contrast we have seen massive amounts of refactoring around the Ruby side of things. Impossible for me to pin this on CS as I have no crystal ball, but it is a fact.

On a personal level I would be happy to never use CS again, I feel my hands are tied in weird ways and it encourages me to write stuff that I probably would never have written in the first place (like 4 levels of nested functions)

---

_[View the full topic](https://meta.discourse.org/t/is-it-better-for-discourse-to-use-javascript-or-coffeescript/3153)._
