Virtual DOM is pure overhead (2018)

Re:Virtual DOM is pure overhead (2018) by concerned_user on Sunday May 19, 2019 @04:39AM (#19952222)

I hear the tale of "soon native Web Components" for years and still none in sight yet.

As far as I remember there are some attempts from Chrome and Mozilla but not sure I saw a real cross-platform spec out, so I stopped tracking the news around it really.

Can you provide some references maybe?

[ Parent | on HN ]

Re:Virtual DOM is pure overhead (2018) by floatboth on Sunday May 19, 2019 @05:37AM (#19952394)

https://caniuse.com/#feat=custom-elementsv1 https://caniuse.com/#feat=shadowdomv1

v1 shipped with Chrome 53, Safari 10 and Firefox 63. (And there's a polyfill.)

It's not "soon", it's very much "been in production for a while".

A base class like LitElement https://lit-element.polymer-project.org is all you need to achieve a sort of "react-like" development style (components with unidirectional data flow) WITHOUT build tools() and WITHOUT dom diffing! :)

() if you want to use npm dependencies instead of just plain files with a bundled version of lit, you still need to rewrite import paths, until https://github.com/WICG/import-maps becomes a thing at least. I wrote a tiny dev server that does that: https://github.com/myfreeweb/es-module-devserver

[ Parent | on HN ]

Re:Virtual DOM is pure overhead (2018) by rxgx on Monday May 20, 2019 @06:11PM (#19965809)

Anyone else get a little excited about that Edge v75?!

[ Parent | on HN ]