I have a huge bias towards functional programming, one core tenet of which is immutability. When I was going through the official svelte tutorial I read this[1] paragraph:
> Note that interacting with these <input> elements will mutate the array. If you prefer to work with immutable data, you should avoid these bindings and use event handlers instead.
Which left me with the impression that svelte's functional story wouldn't be that great. Though I did still finish the tutorial.
As my first project I tried to migrate one of our static websites to svelte with sveltekit. It didn't really feel like I was doing something different than when I was using Vue3/Nuxt3, so I might as well stick with it. I understand that the technical tradeoffs are different, svelte is compiled and has no runtime after all, but the developer experience pretty much feels the same.
> Note that interacting with these <input> elements will mutate the array. If you prefer to work with immutable data, you should avoid these bindings and use event handlers instead.
Which left me with the impression that svelte's functional story wouldn't be that great. Though I did still finish the tutorial.
As my first project I tried to migrate one of our static websites to svelte with sveltekit. It didn't really feel like I was doing something different than when I was using Vue3/Nuxt3, so I might as well stick with it. I understand that the technical tradeoffs are different, svelte is compiled and has no runtime after all, but the developer experience pretty much feels the same.
[1] https://svelte.dev/tutorial/each-block-bindings