sockjs/sockjs-node — comment on commit 7f5e7df67799c3ce9f0db71c9705d21d21656389
File:  line 0
By majek:

I don't mind neither CS nor JS. In fact, the sockjs/sockjs-client is written in pure JS.

But the server side - it doesn't really matter. It's always going to be executed on node, so whether it's written in JS or CS - no difference. I choose CS for:

* the code is shorter
* the code is easier to maintain
* CS has simple inheritance (including `super` keyword) which is exactly what I need, I don't like to reinvent that.
* CS has some features that encourage good programming style (like `bind`, unpack, simpler function declarations), which is what I need.

CS has some disadvantages, but as I said before, it's always going to be run on node, and I ship compiled javascript in `npm`. So unless you're going to hack on `sockjs-node` (in which case you will have bigger problems - you would need to understand my code), you shouldn't really notice that it's CS.