Welcome to syntax. Today we're talking about remote functions and RPC in Svelte.

I'm going to say, off the bat, this is the solution for RPC, for data loading, for anything.

I don't want to use anything else on any other platform, and we're going to show you why.

If I'm using React, it better look like this. So we're

going to be breaking down what these things are, just the general approach for data loading,

how it kind of takes the server client side of it all and makes it really nice and palatable

while keeping a nice separation still.

My name is Scott Tolensky.

I'm a developer from Denver.

And with me, as always, is Wes Boss.

What's up, Wes?

Hey, excited to talk about this, because I dove into several of these, like, RPC libraries in the last a couple of weeks, you know?

And it turns out BetterO Off has one called Better Call.

Hano has one. Eliza has one. Cloudflare has one that's called Cap Cap'n Webb or something

like that. It's Cap'n Crunch. And like there are a lot of the, like this idea of like, obviously

we talked about TRPC. We had them on the

podcast as well in the past, but there's so many different implementations of this RPC, and I'm

excited to see what Svelts take on it is. Yeah, this is something that I think we've both

personally felt. The syntax site is built with Svelk kit. It uses the load functions for data. And I think we've both personally felt the syntax site is built with svelk kit it uses the

load functions for data and I think one of the things that always felt odd about that was like

all of your data all of your you're refreshing your invalidation even your form actions they all

kind of live at that root of the route level, like on any

...