Echo JS 0.11.0

> I sure hope it's not a "few years" though before css-in-js solutions become best practices.

On the contrary, I think CSS-in-JS is quite short-lived. A temporary patch before Web Components become widespread.

> Keep the old APIs, but build a "virtual DOM abstraction" that completely skips the DOM. No more DOM.

The DOM won't go away, there are 25 years of backwards compatibility to support.
And the concept of Virtual DOM isn't the "ultimate thing" of web development. It's not terribly efficient either. The real game changer is the stateful UI.

> It's still predicated on the fact that the DOM and its dom/paint/layout engine is there. We need a whole other engine.

There already is one: it's WebGL. Hard to develop with it? Well sure.
But given that engines improved *a lot* in the past years, why do you *need* all that speed for?

A lot of non-English stuff and a title that's horrifyingly different from the source.

Interesting but not directly related to JavaScript, I'm afraid.
Stay in topic, and use the same title of the linked article.

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.

I meant it should be *state*less, not *statue*less.
It was a silly way to report a typo.

> statueless

But I like statues.

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).

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.

It's impressive how simply requiring a module introduces *new syntax* in Node. I didn't know it was possible.

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?