Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)

Adding a plug for Ractive, with great Mustache/Handlebars templates. We've
mashed up Ractive with the webcomponents polyfill to give us a productive
environment to build our apps.  Kind of a lighter weight Polymer -- we call
it Monomer.

On Tue, Feb 27, 2018, 9:51 PM Joe Pea <notifications@github.com> wrote:

> By the way, React offers the ability to dynamically morph your DOM. This
> is something you don't get with vanilla Custom Elements. You'll end up
> doing in plain JS what React/Angular/Vue and other view layers already
> solve for you. In your example above, you created a static DOM, but that
> example doesn't morph the DOM (declaratively or even imperatively) based on
> state changes. There's real value in these frameworks.
>
> Furthermore more, Vue and React can be compiled at build time, and at
> runtime the DOM manipulation is pure JS under the hood, no parsing at
> runtime.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/w3c/webcomponents/issues/587#issuecomment-369103751>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ACAWh4zMnr7Do5r4oSse4K4Rv62Kw5B7ks5tZL8rgaJpZM4KXuh2>
> .
>


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/587#issuecomment-369104450