Yew: Virtual DOM is too coupled to Yew Framework
Description
Yew's Virtual DOM implementation is too coupled to the framework and should be moved to a different crate if possible. This would allow other backends to be used with Yew in the future.
feature
jstarry
👍4
All 4 comments
Related issues matching "vdom": https://github.com/yewstack/yew/issues/482, https://github.com/yewstack/yew/issues/126
kellytk
on 29 Nov 2019
Related issues: https://github.com/yewstack/yew/issues/343, https://github.com/yewstack/yew/issues/324
kellytk
on 10 Dec 2019
Is there anyway for yew to not use virtual DOM like dominator? What are the implications of not using it? It felt like GC (initial rust) vs no GC (current rust) to me.
pickfire
on 30 Jun 2020
Everything in Yew is pretty tied to the virtual DOM, but I've been trying to think of ways to move away from using a virtual DOM.
teymour-aldridge
on 30 Jun 2020
👍3
Was this page helpful?
0 / 5 - 0 ratings
Related issues
kellytk
路
4Comments
FrontMage
路
4Comments
sackery
路
3Comments
IngwiePhoenix
路
4Comments
sanpii
路
3Comments
Most helpful comment
Everything in Yew is pretty tied to the virtual DOM, but I've been trying to think of ways to move away from using a virtual DOM.