Virtual DOM is pure overhead (2018)
I&#x27;d argue this is essentially just an optimized (and therefore potentially more buggy) virtual dom.<p>Svelte is being smart and skipping comparisons in the places it knows the result is static.  That&#x27;s nifty.  But it also means you have to depend on svelte getting it right every time, in all scenarios.<p>Long term - I think this is probably the right approach, but it feels very similar to the -03 c++ optimization flag:  There was a fairly long period where enabling that flag was considered risky.  Each extra transformation carries opportunities for bugs.<p>It also means extra work at code generation time - it&#x27;s building a vdom engine specific to your template (again - this is nifty!).  Probably not a huge deal, since js build tooling is seeing a LOT of focus on speed, but it&#x27;s there.