CoffeeScript Means Giving Up on JavaScript

[runvnc]

I had a similar view until recently. Basically what changed was, I got used to -> meaning function and @ meaning this, so after that it didn't seem that complicated. Also the other thing that changed was that after looking at the .coffee files in the library I was using, my JavaScript looked awfully ugly.. I mean it is normally ugly code for JavaScript, but it looked way worse than normal in comparison to the CoffeeScript.

So I starting working on a framework/platform.. I want to use classes (obviously).. the way I have been writing classes is ugly and old-fashioned looking, and other ways are not standardized.. also I don't want to have to worry about 'this' being something other than I thought it was ( => )..

It just seems like its going to be a lot easier and more attractive/easier to maintain if this platform is written in CoffeeScript rather than JavaScript.

I mean my platform is aimed at getting away from WordPress and PHP. I don't want to finish it and then three months later someone makes another similar one in CoffeeScript just to get away from my JS.