Can you make it for Chrome too? I've tried some of the Chrome extensions that claim to let you use CoffeeScript, but none of them work as nicely as this.
Back then I failed. It seemed like Chrome didn’t exposed full console and window api to extensions or so. I doubt things have changed since then. But i’ll try anyway.
I had also advocated for improving built-in Safari web inspector, to make it expose reasonable APIs for extensions like this (radar issue #11653556). Unfortunately, without any result.
I use Backbone.js quite a lot, though, so I suppose you could say I am a fan of Jeremy Ashkenas' work, even though I don't like coffeescript. It doesn't solve anything for me - it just makes things a little different without offering any major benefit for me. The article you linked to was an interesting read, I hadn't really thought about it enough to put it into words.
Or, perhaps it'll become a first class language in the browser and then in two years we'll have some other language that compiles to coffeescript...? It seems ridiculous to me, but I don't see why that wouldn't happen.
> I think the best parts of coffeescript will eventually make
> necessary anymore [...]
Anyway, i did not not the "then" trick with classes , like
new class then constructor:-> @param="something
Coffeescript feels to me like the icing on the cake for anyone who understands what the resulting JS will function like.