undefined | Better HN

0 pointsMathnerd3141y ago0 comments

> Svelte's whole selling point was ultra-targeted and efficient DOM updates as a result of the compilation step and not having vdom

Going by performance (https://krausest.github.io/js-framework-benchmark/), Svelte 4 is essentially vdom, Svelte 5 is ultra-efficient based on the direct-DOM approach pioneered by Solid. Svelte 5 is currently a release candidate, API stable but also not necessarily production ready. https://svelte.dev/blog/svelte-5-release-candidate

Disclaimer: I haven't actually looked at Svelte 4 to see why it is so much slower than Svelte 5

0 comments

jonahx1y ago

> Svelte 4 is essentially vdom

I can't speak to perf differences between 4 and 5 specifcally, but I'm pretty sure Svelte's mission has been "no vdom" from the start. Here's a 2018 article, eg:

https://svelte.dev/blog/virtual-dom-is-pure-overhead

ricardobeat1y ago

Svelte first came around in 2015-2016, and never had a virtual DOM - it was actually the one that introduced compiler-based optimizated DOM updates. This is mentioned in the Solid.js documentation [1].

Svelte itself is a successor to Ractive.js which already existed in 2013 [2] with similar ideas, but before JS transpilers came into the picture.

[1] https://www.solidjs.com/guides/comparison#svelte

[2] first npm release: https://www.npmjs.com/package/ractive/v/0.2.0

not_really1y ago

> ...pioneered by Solid

Excuse me what?

Mathnerd314OP1y ago

it is specifically the signals-based approach pioneered by Solid, https://youtu.be/82dzMKZzHrY?t=12314

i-am-fnord1y ago

Aren’t all these techniques a lot older coming from functional reactive programming?

j / k navigate · click thread line to collapse