Comment by afavour 5 years ago And yet Svelte is faster than React in pretty much every benchmark I’ve seen. 3 comments afavour Reply patrickthebold 5 years ago That makes sense though right? One would assume that shadow dom and dom would be slower than direct dom manipulation. thinkloop 5 years ago I'm not sure that's a fair assumption, one of the original sells of a shadow dom was that manipulting the dom directly is extremely slow, so doing as much work away from it is faster. ttfkam 5 years ago Because React's model requires tracking the entire DOM tree for changes and rewriting whole branches where a change is detected.Svelte bypasses the whole problem for the most part. https://youtu.be/AdNJ3fydeao?t=247
patrickthebold 5 years ago That makes sense though right? One would assume that shadow dom and dom would be slower than direct dom manipulation. thinkloop 5 years ago I'm not sure that's a fair assumption, one of the original sells of a shadow dom was that manipulting the dom directly is extremely slow, so doing as much work away from it is faster. ttfkam 5 years ago Because React's model requires tracking the entire DOM tree for changes and rewriting whole branches where a change is detected.Svelte bypasses the whole problem for the most part. https://youtu.be/AdNJ3fydeao?t=247
thinkloop 5 years ago I'm not sure that's a fair assumption, one of the original sells of a shadow dom was that manipulting the dom directly is extremely slow, so doing as much work away from it is faster. ttfkam 5 years ago Because React's model requires tracking the entire DOM tree for changes and rewriting whole branches where a change is detected.Svelte bypasses the whole problem for the most part. https://youtu.be/AdNJ3fydeao?t=247
ttfkam 5 years ago Because React's model requires tracking the entire DOM tree for changes and rewriting whole branches where a change is detected.Svelte bypasses the whole problem for the most part. https://youtu.be/AdNJ3fydeao?t=247
That makes sense though right? One would assume that shadow dom and dom would be slower than direct dom manipulation.
I'm not sure that's a fair assumption, one of the original sells of a shadow dom was that manipulting the dom directly is extremely slow, so doing as much work away from it is faster.
Because React's model requires tracking the entire DOM tree for changes and rewriting whole branches where a change is detected.
Svelte bypasses the whole problem for the most part. https://youtu.be/AdNJ3fydeao?t=247