Echo JS 0.11.0

<~>

MaxArt comments

MaxArt 300 days ago. link 3 points
It's just that `document.all` is a strange and obscure beast. It's a legacy "host" object of the days of Internet Explorer 4 or so.
MaxArt 302 days ago. link 1 point
I meant it should be *state*less, not *statue*less.
It was a silly way to report a typo.
MaxArt 306 days ago. link 2 points
It's worth mentioning that they're not called padLeft and padRight because that would be confusing for strings written from right to left (there's an Unicode code point that marks the text direction, U+200F).
MaxArt 309 days ago. link 2 points
It means that `import x from "y"` is normally a syntax error in Node. But it seems that just requiring @std/esm makes the magic happening.
MaxArt 310 days ago. link 2 points
It's impressive how simply requiring a module introduces *new syntax* in Node. I didn't know it was possible.
MaxArt 311 days ago. link 1 point
WhitestormJS has been linked on EchoJS several times already. It's a very well done framework, but is there anything new or it's just spamming?
MaxArt 311 days ago. link 3 points
Glad you're back. After an improved promise support, now Node has async/await too, which makes everything even sweeter (also, in Node 8.x the performance of promises improved dramatically - not as fast as Bluebird but getting there).

I don't get why so many developers struggled with the async nature of JavaScript, but I guess you're in good company after all.
MaxArt 312 days ago. link 3 points
Again this post? Again with the title different from the original?!
Stop spamming this off-topic crap!
MaxArt 315 days ago. link 1 point
> The return statement ends function execution

That's not correct in some edge cases. Consider the following:

function foo() {
  try { 
    console.log("foo"); 
    return 0;
  } finally {
    console.log("bar");
  }
}

When executed, it will print both "foo" and "bar".

Also worth mentioning that a return statement inside the finally branch with override any previous one.
[more]