Yeah. Nicely, I don’t know that I can provide you a pithy model of what it means both… However there’s a – what are runes? I imply, I used to be attempting to grasp it. I say, “Okay, runes, they’ve part of the syntax, their key phrases, they’ve a greenback prefix, they usually seem like capabilities.” Truly, what these remind me numerous is kind of a combination of issues we’ve seen previously. So that they’re utilizing runes to switch a number of the previous reactivity primitives that Svelte had. They usually’re doing that in a manner so that you just’re beginning to use extra useful syntax.
Truly, once I was taking a look at it, it jogged my memory numerous like Vue’s Capabilities API for doing knowledge administration, the place you kind of wrap some state in a operate, and now you’ve this good little reactive primitive you could cross round and do enjoyable issues with. Distinction from that – you don’t must import them from wherever. They’re a part of the language.
So Svelte continues to lean into this “We’re defining our personal language that the compiler makes magic for you.” Nevertheless it provides you a set of primarily knowledge primitives that allow you to outline reactivity. And it form of felt like – yeah, this mixture of the Vue Capabilities API, and one thing that I’ve seen with Qwik, the place they use the greenback signal to point, “Hey, this operate is particular. The compiler goes to deal with it specifically.”
Now, I feel within the Qwik world, you try this with arbitrary capabilities. With Svelte, if I’m understanding accurately, they’ve a set of capabilities that simply have this greenback signal, the place it’s like, okay, right here’s these 1, 2, 3, 4, 5, 6, 7, if I’m counting accurately… Seven particular capabilities that the compiler is aware of about, you don’t must import, that then have explicit habits out within the wild, and you should use them to implement reactivity.
