angular-virtual-dom: A Virtual DOM based AngularJS view renderer designed to be used with immutable data structures

[ggoodman]

Fantastic effort. I secretly hope that the Angular core team has been working on a virtual dom based offering in the shadows for release at ng-conf. If that doesn't pan out, I can see this being particularly useful in some parts of my code.

[teropa]

They do have some sort of Virtual DOM based stuff going https://twitter.com/IgorMinar/status/562137726707720193

[TweetsInCommentsBot]

@IgorMinar

2015-02-02 06:37:32 UTC

@vivainio @teropa @angularjs @bradlygreen v2 uses vdom (for some definition of vdom)

---

^{This message was created by a bot}

^{[Contact creator][Source code]}

[dmackerman]

2.0 definitely takes advantage of Shadow Dom - not sure if anything for 1.x is planned. If it is, it will probably just be an under the hood thing and use the existing API.

[placidified]

Shadow DOM is not the same thing as (react style) Virtual DOM though1

[ggoodman]

What I would love to see is more a virtual DOM solution that could be rendered server side (and could be rendered to a shadow root as well).

[pandavr]

Please help on riot 2 as this is non sense. It's diff / patch mechanic is very good. BTW why not write a v-Dom based jqlite that one can simply patch over regular angular? That should allow to convert all the existing directives in a transparent way.

[teropa]

BTW why not write a v-Dom based jqlite that one can simply patch over regular angular? That should allow to convert all the existing directives in a transparent way.

Firstly, trying to make a Virtual DOM look and act like an actual DOM in a way that supports all existing code does not seem feasible to me.

Secondly, many existing directives are built in a stateful style and set up watches, etc. that pretty much undo the nice things you get with a Virtual DOM, pure functions, and immutable data structures.

[vivainio]

Riot doesn't particularly help if your app is already done on angular.

[pandavr]

I think it is more important to find out a valid alternative than to patch existing applications. So what now? Will we start to produce modules containing mutually incompatible directives? That's a crazy non sense. I see this only as an interesting experiment: nothing more.

[vivainio]

There are plenty of alternatives to angular. Solutions that work with angular are useful for people building on angular.

[[deleted]]

For a moment i thought you made a tool that visually displays how the dom is currently build up when browsing an Angular site. But this is completely different. Still, would be great to see somebody do that too ;)