I don't really know much about the coffeescript community, although being totally honest, as a detached observer I do get a whiff of a "chip on the shoulder" ki

I don't really know much about the coffeescript community, although being totally honest, as a detached observer I do get a whiff of a "chip on the shoulder" kinda attitude. Perhaps no different from any language though. 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. I don't really like being a naysayer about technology or sticking my head in the sand. I think the best parts of coffeescript will eventually make their way into Javascript and then coffeescript won't be necessary anymore (unless it also continues to evolve). In which case, browser support for it seems unnecessary to me. 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.