Ok, so coffee script is great.

...but really? This is a totally unexciting minor point release with basically just bug fixes; no major new functionality or interesting features.

Who cares? Why is this rising on the front page?

(no seriously, am I missing something?)

Yes. It's great to see projects moving forward, but minor incremental releases don't tend to make great HN posts, except when there's something unusually interesting about them.

As jashkenas (CoffeeScript author) has stated, he considers the language "complete".

https://news.ycombinator.com/item?id=7139807

Also, this just links to the homepage, which has nothing to do with the title. Can someone please either change the title to "CoffeeScript Homepage" or update the link to a changelog?

For the curious – http://coffeescript.org/#changelog

Still no generators/yield support :(

https://github.com/xixixao/coffee-script

I just include this is my package.json at the moment.

    "coffee-script": "xixixao/coffee-script"

Have been for the last few months. It uses --> and ==> for generators with version 1.7.1

The only issue I've found with this fork is "if not yield something()" results in a syntax error, but "if not ( yield something() )" works as expected.

Just fork it to your own repo and forget about it until it's added in stable.

You're going to wait a long time for that. I would personally look for an alternative as I feel the project is not being managed properly. Where is CS road map ? there is none. I hope people will definetly move to CS redux ,which seems to be to CS what lodash is to underscore. Same for Backbone,what's the roadmap ? and noone sees a pattern here ?

Somewhat to the side of your main point, but curious what you would be looking for Backbone to add that it needs a roadmap for. I'm not so sure that everything needs a roadmap and to be developing new features. Backbone is IMHO a great example of something that already accomplishes exactly the job it is meant to do, and if you want to do anything else that is your business.

I think Ampersand is the analogue for Backbone. It does the same stuff, but it fully embraces modules, npm, and browserify and it's got great computed properties. These days I work mostly with React, but if Ampersand had existed a year and a half ago I'd have been all over it.

http://ampersandjs.com/

This is incredibly frustrating. It has been sitting around unmerged for nearly a year because they can't decide what the syntax should be. Someone ought to just fork it.

CoffeeScript novice here. Can someone please tell me why/why not coffee script should be used rather than JS? Is it usable in serious prod level projects? Looks very clean.

It's definitely usable in serious production-level projects. I use it regularly and quite enjoy it. I don't have much time right now but to sum it up: it takes the (IMO hidden) expressiveness of Javascript and brings it into the light.

I feel like it gives me a 10x increase in productivity when coding JavaScript projects. I consider it irresponsible to not use it.

All of my projects have been in Coffeescript since 3 years ago (over 100k lines of code). Have had almost little to no problems. Like you, feel 10x more productive when I'm using it!

As fair as I know it's used by Palantir and Dropbox in prod (just to name the big ones).

coffee-maven-plugin 1.4.11 (https://github.com/talios/coffee-maven-plugin) with 1.8.0 support/defaults has just been released to Maven Central for anyone building coffeescript under the Apache Maven build system.

  <dependency>
    <groupId>com.theoryinpractise</groupId>
    <artifactId>coffee-maven-plugin</artifactId>
    <version>1.4.11</version>
  </dependency>

HN doesn't allow resubmission of the same link that points to the change log [1], so here's the change log:

    The --join option of the CLI is now deprecated.
    Source maps now use .js.map as file extension, instead of just .map.
    The CLI now exits with the exit code 1 when it fails to write a file to disk.
    The compiler no longer crashes on unterminated, single-quoted strings.
    Fixed location data for string interpolations, which made source maps out of sync.
    The error marker in error messages is now correctly positioned if the code is indented with tabs.
    Fixed a slight formatting error in CoffeeScript’s source map-patched stack traces.
    The %% operator now coerces its right operand only once.
    It is now possible to require CoffeeScript files from Cakefiles without having to register the compiler first.
    The CoffeeScript REPL is now exported and can be required using require 'coffee-script/repl'.
    Fixes for the REPL in Node 0.11.

[1] http://coffeescript.org/#changelog

Just put the version number in the query string:

http://coffeescript.org/?1.8.0#changelog

You can resubmit a link by changing the url slightly. For the policy on reposts see the FAQ.

We changed the url to the changelog.

Thank you @dang & @CyberShadow