Why this runes? It makes svelte look like React and I hate it(Personal Opinion).

[ananduremanan]

For me

<script>
	let count = 0;
	$: if (count > 10) {
		alert(10);
	}
</script>

<button onclick={() => count++}>
	{count}
</button>

is better than this

<script>
	let count = $state(0);
	$effect(() => {
		if (count > 10) {
			alert('Too high!');
		}
	});
</script>

<button on:click={() => count++}>
	{count}
</button>

felt like the magic of let was gone..😒

[JLAcostaEC]

mmmm, I understand that you may feel that it is similar to React, but you must understand that all this has been done to have much more control and more optimization of your application, as well as allowing you to bring reactivity outside the Svelte components (component.svelte.ts) or (store.svelte.ts)

Yes, Svelte pre v5 was too magical, but as the app grew you could see how certain limitations appeared. Including the fact that the bundle size grew a lot more as your app grew.

As you program more in svelte 5, you will realize that the control over your app is now much more polished, in addition, you will see that in terms of optimization, your app size will be less and will be faster (you can see the benchmarks that put Svelte almost at the same level as vanilla JS, something that no other framework achieves)

Following the ideology of MAGIC let was like a very big spell to solve everything. While runes are very specific spells to solve each type of problem, in effect you go from being a magician with a single skill to one with many and each of these are much more powerful.

[JLAcostaEC]

If it is true, it is not necessary in all projects, but have you asked yourself why Svelte is not used in almost large (enterprise) projects? Precisely because of not being able to control things better.

I'll tell you this, and this is my personal opinion: I think the fact that they replace features between major versions is good for the technology. All of this is brutally necessary and if it weren't, then we would still be using jQuery 3 with PHP and trying to do MAGIC to solve a problem. Don't get me wrong, at first I also thought this change to svelte was a mistake. But I gave him a chance, and now I don't want to do anything outside Svelte 5

[ananduremanan]

Imo, it feels like runes were created for the minority who needed that control, and I admit it's great to have the solution for that. It feels like a design choice to attract react devs to svelte and I personally feels like the developer experience was now bloated with more boilerplate codes. Beside all ur points on why we need this in svelte, I'm just sad to see my favorite tool try to mimic react.

[mbokil]

I used to use Vue 3 a lot but then when I saw Svelte 5 I felt right at home with a proxy based reactivity system. The older reference based reactivity in Svelte 4 is what kept me from using it. I felt it was awkward to have to re-reference your data to get the UI to update. Just updating a property in an array of data and letting the reactivity system handle the UI seems like a better design to me. More efficient and fine grained reactivity. I think it was a smart move since it is drawing in the React hooks and Vue devs.

[brunnerh]

Just updating a property in an array of data and letting the reactivity system handle the UI seems like a better design to me.

That was also possible in Svelte 3/4. You only need dummy assignments if something modifies state internally, e.g. an array push.

I think it was a smart move since it is drawing in the React hooks and Vue devs.

This was not the goal/reason for the API changes.

[mbokil]

It might not have been designed that way but it is definitely helping us since the reactivity systems are closer now it is faster to migrate to Svelte 5.