3 ms·
Also IcedCoffeeScript http://maxtaco.github.io/coffee-script/ http://maxtaco.github.io/coffee-script/ It's just CoffeeScript with await and defer keywords, es
by babby 13y ago
Also IcedCoffeeScript
http://maxtaco.github.io/coffee-script/ http://maxtaco.github.io/coffee-script/
It's just CoffeeScript with await and defer keywords, essentially.
I personally would never touch toffeescript/coco and friends as they differ too much for CoffeeScript, which already segregates the JS userbase enough. I figure IcedCoffeeScript is the lesser evil for compile-time control flow as it's not adding a bunch of other changes to the language that users have to understand to contribute to a project written in it. Another issue with these CS spinoffs is; what if the main contributor says "Fuck it" and bails? CS itself is big enough to have a lot of talented contributors. What happens when CS moves over to CS 2.0 ie. coffeescript redux? Do these spinoffs need to recoded?
That being said I probably won't use Iced either, as much as I want to... Maybe I'm all wrong about this? Maybe this userbase segregation crap is not as big a deal as I may think.
- ilaksh 13y agoI only use that one feature from ToffeeScript as shown in my example. Obviously much cleaner