I use to be one of the biggest defenders of CoffeeScript: http://procbits.com/2012/05/18/why-do-all-the-great-node-js-developers-hate-coffeescript
I've since changed my tune quite a bit. It's not that I think that CoffeeScript is inherently bad. My problems are as follows:
1) In the Node.js ecosystem, if you're going to write modules for others to consume, you should write them in JavaScript if you expect some sort of adoption or contribution.
2) CoffeeScript can deceive JS newbies into thinking that it solves JS's problems. You should really have a solid grasp on JS before starting CoffeeScript.
3) I since came to the conclusion that CoffeeScript doesn't offer much more than JavaScript. The lines of code that it tries to convince you that it saves, is only true if you compare CS to the compiled JS output. But in practice, the margin is much smaller.
I use to write everything in CoffeeScript and have since converted over exclusively to JavaScript. If you want to write CS for your own app or your team's app, go ahead. But if you write OSS, don't expect as much contribution as you may get as if you wrote it in JS.
I upvoted this because I agree with post.
I don't think he was eloquent enough in his rant or made his points clearly. But I do agree with his sentiment.
It's fine that you think CS gives some "new points of view". I just don't see it and personally it annoys the hell out of me when people post/commit CoffeeScript code instead of JavaScript.
(ps - I've been using coffeeyesplease nick since 1999 :-)
I don't like it because it doesn't even support getters and setters and will definitely lag behind for too long after new features start to become more mainstream. Other people don't like it because of many other reasons.
The point is, the libraries and snippets of code written in CoffeeScript are advertised in various communities like S.O. and GitHub as if they are written in JavaScript.
This is arrogant and needs to stop.
egecan, I noticed that you mentioned you are looking for an easy way to define getters and setters, have you checked out www.jTypes.com recently? We just added a new AIP syntax that makes it really easy to define getters and setters:
https://scontent-a-lga.xx.fbcdn.net/hphotos-prn2/1383208_385694174892987_509646233_n.png
You also mentioned that you don't like CS because it will lag behind for too long after new features start to become more mainstream. This is not the case with jTypes, as it plans to fully utilize many of the upcoming features found in ES6 (especially since it's emulating that behavior now). I just posted a more detailed description of everything here: http://www.echojs.com/news/6571
Lastly, as you touched on, CS is not JS, and should not be advertised as such. jTypes on the other hand is written natively in JS, and is simply a library that you include. If you're only looking for encapsulation, I would highly recommend jTypes Lite, and it is only 5 KB gzipped (14 KB minified).
I am always looking for feedback and suggestions for new features, so if you have any questions or comments, I would be happy to hear them and answer them!