I really didn't get all this from the official communications, I always just thought it was a one-to-one conversion to a different way of writing things. Your explanation of how signals are implemented and doing it live gave me a nice eureka moment, it's all clear now. Thanks!
Thank you for this video, this helped bridge the gap between stores and runes for me to some degree. i wouldn't call myself the best at using subscribing/ unsubscribing methods from stores but i will admit i struggled greatly in trying to make complex components that relied on asynchronous data in a SSR context. would love to see some examples of components from you that really drive home the idea of thinking in 'reactive value' rather than in terms of functions that call other functions.
Thank you for your feedback! Admittedly SSR isn't exactly my area of expertise as I've primarily worked on single page apps, but I can definitely make some examples of solving real-world problems using stores vs using runes if that would be helpful?
Thank you for your comment! That's a major point I'll be making in my next video. There are reasons why $effect shouldn't be used that are not so obvious but really important. If you understand how $effect works under the hood via queued microtasks versus how $derived works using flags, you'll see the sheer amount of gotchas that can happen if you use $effects when you should be using $deriveds.
Hello, I'm wondering at around 22:20 mark when you set the age to 45 the effect runs, loud and clear I understood that. But after you set the age to 45 you set the message "you're really over 35" and the "effect" doesn't react to it. Is it because the assignment of the message variable to another string is done too fast? Also I appreciate a lot the explaining of the shift in thinking, I've been working with Observables in Angular for 5 years now and it's all about subscribing/unsubscribing there
Good question. This over-simplistic version of the Svelte reactivity library I created for the example in this video doesn't incorporate an important part of the Svelte runtime which is basically that effects will run only after the current synchronous task is completed. In this version, effects run synchronistically. In actual Svelte, all of the synchronous calls and assignments complete, and then effect would is marked as dirty, it runs only at the end. In Svelte, in a script like this, you would actually only see one output with the final value. For this mini signal framework though, to actually answer your question, I think the reason why it didn't update the last line is because I didn't scroll down enough. Either that or I made a little mistake somewhere programming it. But there's no point in trying to unpick that because actually it doesn't reflect what really happens in Svelte. Fundamentally, because you asked this question, it means you grasp what I was trying to convey in this video, which is the fundamentals of how signals work. I'll be releasing another video very soon that explains the actual reactivity system in-depth and will be a lot more true to the "marking dirty" aspect of Svelte. This will explain the microtask queue which is very important and will give you a true-to-Svelte answer for your question.
