DEV Community

Discussion on: DOMs Decoded: DOM, Shadow DOM & Virtual DOM

Collapse
 
ruppysuppy profile image
Tapajyoti Bose • Edited

I didn't get what you were asking. Shadow dom isn't a dom, it's a technique to nest a dom in another

And regarding the dom updates, I did mention that part in the virtual dom (dom updates are one of the slowest operations in web dev)

Collapse
 
ksengine profile image
Kavindu Santhusa

Very sorry. It's a mistake. It should be virtual DOM.

Why browsers can't implement the part of virtual DOM?

Thread Thread
 
ruppysuppy profile image
Tapajyoti Bose

That's a very good question. I didn't have an answer to it, so I looked up Google. The general theme I found can be summed up by this comment:

If you follow the JS world - it was pretty much the same with Promises - we got the bluebird and jQuery implementations, but at the end Promises went native and all those libraries and frameworks are no longer needed.

People were saying that browsers would slowly start using the virtual dom, but I am not entirely sure when it would happen as it has been years since the concept of virtual dom was introduced

Thread Thread
 
ksengine profile image
Kavindu Santhusa

Thanks for the answer for burning question,

It's irrelevant to JS world. As this feature could improve performance of browsers, It's an optimization to browsers. So relevant to the world of rendering engines.

First Promises are added to the JS spec, So browsers should implement that, But virtual DOM can be added to any browser individually.

Thread Thread
 
ksengine profile image
Kavindu Santhusa

I thought to create a JavaScript framework without virtual DOM.

Nowdays computers are more powerful. Real DOM is enough if developers are using it with a responsibility.

I am looking for collaborators for it. I you can please contact me via ksengine.github@gmail.com.

If this comment looks spammy, I am sorry. You can inform me and I'll delete this.

Thread Thread
 
ruppysuppy profile image
Tapajyoti Bose

No worries, you can keep it