I'd love to know why you think Moon is ridiculous, so I can try to improve it. I honestly think what you're doing here is really ridiculous, try and give some feedback instead.

Edit: Sorry, I misunderstood your comment. I interpreted your comment as saying all of these new frameworks are making things ridiculous. This implies that Moon is contributing to that, and I'd rather have feedback.

He never said Moon is ridiculous.

Your English comprehension is really bad. How's that for some feedback?

Incivility and acerbic swipes will get you banned here. You've done this many times on HN, unfortunately. Would you please fix this? Among other things, it sets the wrong example for the less laconic.

Yes, we're going to lock ourselves in that building any day now, just as soon as the Operating System people come out.

browser vendors need to do this.

we need a standardized declarative dom patching mechanism with data-binding that has optimal perf so we dont need to keep reimplementing virtual-dom.

Over in Polymer, we're exploring ways to do exactly that: https://github.com/PolymerLabs/lit-html

Template literals in JS give us a way to always tell the static from dynamic parts of a template. HTML <template> elements let us stamp out pre-defined trees of DOM quickly. Combined we can then only update the dynamic parts without a virtual DOM.

Also see hyperHTML [1] which is same idea, but predates lit by some months. Comparison here [2].

[1] https://github.com/WebReflection/hyperHTML [2] https://gist.github.com/WebReflection/fadcc419f5ccaae92bc167...

were you aware of https://github.com/trueadm/t7 when you started?

are there advantages over t7, other than NIH?

T7 is quite a bit larger than lit-html, and requires a vdom reconciler still. lit-html is self-contained and < 2k minified and gzipped.

I also didn't want to use vdom because it doesn't encode whether nodes are static or dynamic, and even static sections are diffed. That's extremely important feature for performance and memory overhead, which is why I'm happy to see that emphasized in Moon.

Also, coming from the Polymer team, where we've had a lot of success using <template> elements to stamp out large pre-defined DOM trees, I wanted a system backed by those.

thanks for the details.

This is a common thought: https://xkcd.com/927/

You could point to frameworks which have had majority usage at any given point and say those were the "right" ways at the time. But ideas evolve, which isn't so ridiculous.

probably the most over-used xkcd reference of all time.

The correct analogy would be "There are 14 competing standards with a new one released each week that creates doubt about the ongoing use of existing established standards and know one knows what the fuck is going on".

Do you want an open ecosystem or a controlled one? There is no in between, and you will hate it no matter what you choose. On the Open ecosystem side of things you have things like Linux with 10,000 independent distributions doing slightly different things. On the controlled you have Microsoft, Apple, and Oracle telling developers the "right" way to do things.