@sveltejs Congrats to the Svelte team! Looking forward to continuing to work with you all on the design of a new JS standard for Signals that we can all share.
@sveltejs awesome work, this looks like it will solve pretty much all of the mildy inconvenient things i run into
@sveltejs All frontend frameworks adapt signals step by step 😁
@sveltejs Thank you for ruining 80% of what was good about Svelte: Fine-grained reactivity. In v5, a change to one state variable triggers re-runs of all expressions in the markup and I'm supposed to believe that's a good thing.
@sveltejs The article itself makes runes appear more React like (initial reaction: is this a step backwards?) but the video clears it up a ton: youtube.com/watch?v=RVnxF3…
@sveltejs I genuinely don't understand why these `get` and `set` properties are necessary. Something about the mental model is not making sense to me. Because $derived breaks function rules, I feel like it's not that hard to just replace `done` or `text` with a reactive reference too.
@sveltejs Missed the chance to use Unicode Runes: const count = ᛊ(0); const double = ᚤ(count * 2) ᛟ(() => { console.log(count); });
@sveltejs So this is much like ref in Vue? let countRune = $state(0); countRune += 1; let countRef = ref(0); countRef.value += 1;
@sveltejs It's... Vue 😅 Looks like direct port of Vue reactivity to Svelte.
@sveltejs @Rich_Harris I can't seem to take my eyes of your right eyebrow. It remind me of a chinese emperors 😅 But Runes is 🔥
@sveltejs Where is the dependencies array for $effect?
@sveltejs Console logging doubled stays in sync with github.com/Rezact/Rezact#… without runes:
@sveltejs This seems bad, is Svelte now compiling reactivity into regular .ts, and .js files now? I don't see how this is possible without compiling and subsequently changing the underlying js logic. The rest of Runes looks good, makes the api closer to other reactive systems.
@sveltejs we are going full circle again, i really like svelte and this removes the best of svelte for something that is more like solidjs/react this would be great as a extra tool but not as the recommended/right way to write svelte
@sveltejs 😩😩😩 You dragged us to the Darksider
@sveltejs 🍿What in the actual vuejs is this? Kidding. Sure some of the syntactic sugar is lost, but trying to refactor store logic from .svelte into .js/.ts was always a huge pain point for me. If in addition the performance is at vanillaJS levels ... why not?
@sveltejs So why use svelte now that it is like any other framework ? Genuinely asking
I was curious about why `$derived` were designed this way ``` let { width, height } = $props(); // instead of `export let` const area = $derived(width * height); ``` instead of ``` let { width, height } = $props(); // instead of `export let` const area = $derived(() => width * height); ``` This really breaks how people run JS using their brain. `width * height` create a function scope under the hood and will be executed lazily.
@sveltejs how long till we will be able to fus ro dah?
@sveltejs So please join forces with Vue finally and make us happy. Let the two wonderful communities work together for a better future! 😊👍
@sveltejs The best part of this video is how well represented I felt by this ...
@sveltejs this is funny: youtube.com/clip/Ugkx-dtLt…
@sveltejs I really like the runes syntax and stuff so far. Nice work!👍 The one thing that I'm a bit worried about is that I can not create and export custom stores from outside components in the preview. Is this something that will be supported in future versions? Example:
@sveltejs Feels like svelte is killing a main reason people use it: Simplicity