Rich Harris - Svelte

Full Stack Radio
|

Automatic TRANSCRIPT

The best place to start though would just be talking about spelt itself and I. think that'll probably lead into a kind of how you think people should be building Steph for the web. Because I'm sure there's a lot. Of, you know things they're related So so what does like the pitch I? Felt these days after you know having time to refine it over the last few years. Still working on the pitch on the it's a little bit of a difficult thing to to summarize and what I found works best is to try and PUT IT in the context of projects that people Germany more familiar with. So little people who've used reacts a lot of people who view. And they used to this idea of building web applications out of self contained components where you have the mockup for a particular piece of you I together with the styles that with that mockup and the behavior that controls how you can interact with that markup, and what it will change into in response to changes in state of Europe. so is that is the thing that allows you to build. Applications components the difference between spelt, and there's the projects is that? It primarily things of itself was a compiler, whereas traditional framework will take your to the author components and then sort of tandem into instructions to the browser at runtime. Spelt tries to do as much as possible at bill time, so you integrate your usual bill stat using web, tackle roller, or whatever module Bundy using, and it will take. The components that you've offered and an literally writer as Vanilla Javascript. And through that, it's able to achieve typically much better performance than traditional framework, and because we don't need to carry around in a virtual bum, defend general any of the stuff that you normally expect to include. Your application will typically be a lot smaller as well which means that it gets to use a faster and it starts up faster. the the final major benefit of a compiler century designed is that we have a lot more control over the Olsen experience when not constrained by having to. Design components in a way the the is. It like it's, it's not. We don't have to be valid jobs rich. And spelled component actually isn't written into a job. Script file is written to a file which is a super set of HTML so you're literally just writing html orienting it with the. Type cutty. Brace job expressions that you need for it to become dynamic, and because of that we can also include styles into component in the same file, and they will be scoped to the mockup. Because the compiler can analyze in the context of the MOCKUP. And you can have local state which you, which you change just by reassigning to triggering, renders in a more granular fashion than than the typical component level mandates, so it's a combination of all of those things it's framework, but it's also a compiler, and it's also a library of the things that you need when you're building an application, and A philosophy of building APPs I. Guess Yeah

Coming up next