Since the reference part points to ECMAScript (without being in the syntax of ECMAScript), I am simply guessing that it is extremely similar to coffeescript that entails a nearly one-to-one bindings to JavaScript.
However I am in no way seeing it sigificantly easier to code than JavaScript itself, given that it's again prototyped language, and it again subjected with the same problems JS has.
There is some interesting aspects of this language though, e.g.
after {delay: 3000} ^{ print "3 seconds later" }
the thing is after returns an "executor" function which get called with a lambda function. If the same thing has to be written in coffeescript:
looks not as elegant, as the parameter of the first function call can't be passed without parentheses.
(implementing "after" in coffeescript)
after = (a) ->
a? and typeof a == "object" and (arguments.keywords = a;a = a.delay)
if a
if typeof a isnt "number"
throw new TypeError '"delay" argument must be a number'
(fn) -> setTimeout(fn,a)
Since the reference part points to ECMAScript (without being in the syntax of ECMAScript), I am simply guessing that it is extremely similar to coffeescript that entails a nearly one-to-one bindings to JavaScript.
However I am in no way seeing it sigificantly easier to code than JavaScript itself, given that it's again prototyped language, and it again subjected with the same problems JS has.
There is some interesting aspects of this language though, e.g.
the thing is after returns an "executor" function which get called with a lambda function. If the same thing has to be written in coffeescript: looks not as elegant, as the parameter of the first function call can't be passed without parentheses.(implementing "after" in coffeescript)