As I alluded to on my stream with @RyanCarniato, one of the great things about Svelte 5's runes is that the compiler can determine whether or not something even needs to be backed by a signal. Signals are great for updates, but can have a non-trivial cost on page load when the relationship between the bit of state and the UI is trivial. Grouping DOM updates in singular effect signals can reduce that cost. In fact it's an interesting topic as the raw approach of virtual DOM libraries often avoids the allocation costs here, especially if they skip diffing the template part entirely (like Million.js, Ivi and Blockdom). Reducing unnecessary allocations and memory consumption always results in better performance.