Creating Reactive Browser APIs In Svelte

[@abtix]

10:45 wait I'm a little confused. What makes the $effect or "get current()" rerun when this.#version changes? I thought it had to be inside the effect for it to trigger.

[@abtix]

I sort of understand it now. Every time this.#version or anything reactive inside a "get ...()" changes, the get will rerun. I just don't understand why. Maybe it's a Svelte thing, maybe not.

[@dei8bit]

your intro sound is like when you connect an USB like i feel that i connect with the video ready to receive your sacred bits of information :$

[@jazza231]

1:35 The Svelte

[@camoman1000]

A great video would be to combine the context api and createSubscriber

[@Antonio-fo4fl]

I think what's confusing for me is why does something like subscribers or even position at the end in the mouse subscriber does not need to be state sometimes. I guess at that point svelte would track it so you would need to wrap it in untrack likely so we don't run the effect when it changes but for some reason my brain is struggling with it lol. Need to remember state is only for stuff you want svelte and it's api's specifically to react to, but I don't know why I struggle with the fact that subscribers value is being changed behind the scenes

[@hyperadapted]

11 seconds ago is wild

[@alight4045]

I think now svelte have more chaos just bcs of runes plus writable,set and $ much more reactivity in chaos manner, i think its better to have clear method of getting things done in different ways

[@JoyofCodeDev]

you don't use them both unless you have older code that needs to be updated

[@alight4045]

@@JoyofCodeDev I think there is a lot to improve in runes and a lot to do with it, I am big fan of svelte and thank u for ur support

[@tithos]

This is game changing!!!

[@PhilSherry]

$effect.tracking example, especially for Scott Tolinski. 😅

[@JoyofCodeDev]

the docs need some love