4 ms·
I don't think it's as important as you might think (but maybe I'm just naive). I've been developing a game in CoffeeScript for over 2 months and I've yet to ne
by tieTYT 13y ago
I don't think it's as important as you might think (but maybe I'm just naive). I've been developing a game in CoffeeScript for over 2 months and I've yet to need a source map. Every time I get a runtime error, the javascript is easy enough to understand to figure out where I made my error in my CoffeeScript code. And, maybe it's naivety, but I can't imagine having a source map making that feedback loop any faster.
Of course, CoffeeScript is probably way closer to the javascript it generates than Haste and ClojureScript are. That may make all the difference. For the 3rd time now, that may just be my naivety :)
- davesque 13y agoCoffeescript might not be the best example. It strives to be a "symbiotic" language which emphasizes the finer aspects of the host language (Javascript) by introducing special syntax. It tries to avoid constructs which would require any kind of virtual-machinary in order to run. As a result, Javascript code compiled from Coffeescript is pretty easy to follow. I'm not sure the same could be true for Javascript compiled from a language like Haskell.