Yeah - this has been posted way too many times. There was some work on significantly modifying the CoffeeScript compiler to add static metaprogramming (macros+more) but I don't think it's gone anywhere recently - https://github.com/fab13n/parsec-coffee-script.
The real point of the article was to draw attention to how extensible the CoffeeScript compiler can be. Jeremy talks about this when presenting the language and it's recently been used in a couple interesting ways like contracts.coffee (http://disnetdev.com/contracts.coffee/).
I've been paying for Spotify in the UK and been using the desktop client without any tricks in the US since moving here. The big problem is that the Spotify iPhone app isn't available in the US app store. Is there anyway around this?
Grooveshark is great and since moving the US I've used it a lot. Where I think Spotify wins out over Grooveshark is the quality of their music library. I frequently find that albums on Grooveshark are missing tracks, in the incorrect order, or are incorrectly named. I guess it's a little thing but it feels like a big difference.
By "in flux" I was intending to vaguely refer to the problems with the protocol which has led Firefox and Opera to ship with WebSockets disabled. I'm guessing we're probably going to see some changes to it in the future. Hopefully sooner rather than later.
The WebSocket protocol is still very much in flux. This drop is only to give an idea of the server side API would look like (I think anyways). I imagine as the protocol calms down they'll implement whatever's decided on.
The real point of the article was to draw attention to how extensible the CoffeeScript compiler can be. Jeremy talks about this when presenting the language and it's recently been used in a couple interesting ways like contracts.coffee (http://disnetdev.com/contracts.coffee/).