วีดีโอ

Thanks! I've had an outline for the fourth video but I've been so busy these last few months I haven't really had the chance to make it. It's definitely on my bucket list!

That's the idea. People may be tempted to use $effect as a way to continue some logical process (when this changes, then do that), but that logical process can more often than not be solved using $deriveds, or even just plain old functions of the original $states.

My tutorials presuppose that you have some foundational dev experience, so they may not right for you. If you're a non-dev I'd suggest learning the basics first. Svelte 5 is already a release candidate - so past beta already.

Thank you! I appreciate the feedback. It's not an error - I have plans for a part 4 and even a cheeky 3.5 potentially. It's just been busy around here. Can't make any promises as for when but it's definitely on my agenda :)

That's a little project I created, link is in the description. Read the readme so you don't get too confused. The syntax doesn't match Svelte exactly but it's reasonably close but without some of the extra optimisations like proxies (for the time being).

Thank you! I had a bit of a back-and-forth with that idea. I mean the point of nano is just to get people's head wrapped around signals & svelte 5, hence why it loosely replicates the compiled code of svelte 5. But it's probably going to evolve as I implement new features, so probably shortly after I make a video it will be outdated anyway. I'm still on the fence! I tried to put as much thorough documentation and explainers in the nano source code though.

@@petermakeswebsites That makes sense. I think what I'd love to personally see is how you implement signals in general, so it's not so much understanding the Nano code itself but the general approach. Like, what are the key parts that every implementation has vs. the parts that are specific to Nano. For instance, I'm curious if the DepTracker pattern you use with static instance variables is a common pattern.

Arg! I'm trying to find a setting for stable volume but can't find it anywhere :(

Thanks! And yes, however I do think that there are some losses moving from Svelte 4 to Svelte 5. A lot of those nay-sayers have some valid points. There are some conveniences that have been stripped away, and Svelte 5 I find actually requires a bit more of a technical understanding whereas Svelte 4 it was easier to just jump in. Svelte 5 I believe will scale more cleanly, though, which works for my particular use cases. In any case, like you say, you need to understand Svelte 5 fully before you can pass a judgement...

​@@petermakeswebsites Yes, but conveniences should never overshadow functionality. While they should complement each other, functionality must take precedence. Regarding Svelte 5 requiring a deeper technical understanding, that's not necessarily a bad thing. As you demonstrated in the video, Svelte 4 had behaviours that didn't align with JavaScript standards, whereas Svelte 5 does. The main issue I see is the documentation for Svelte 5-it's quite brief and to the point. If there were a more descriptive way to reveal what's happening under the hood, the higher technical requirement would be less of an issue. With Svelte 4, I never fully understood how its reactivity worked. It was more a case of "okay, this works 🤷‍♂" without knowing why or how. While the magic $: syntax is simpler, I'd rather want to improve my JavaScript skills while using it a framework.

Hm thanks for pointing that out, I think I edited this video with different software. Good to know for the future...

IMO they are all a bit low

@@W4nn3 I'll check the levels for all of them next time

Thanks for your comment :) it means a lot!

Thank you! Is there anything in particular you're not clear on that I can emphasise in a future video?

​@@petermakeswebsites I think the following video addressed everything pretty well 👍

Thanks for your feedback! What parts feel unclear to you?

@@petermakeswebsites not unclear but I have to sort it out in my head the way I'm thinking 😁

This is exactly what I want to hear! I'm happy this was useful for you... Thank you for your comment and feedback :)

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.

I'm glad to hear that! I felt the same. I'm going to be making a much more in-depth video very soon that will clarify a lot more. Stay tuned!

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.

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?

@@petermakeswebsites yeah will still be appreciated