Welcome to syntax. Today we're talking about standard schema. Schema. That's a word I'm going to

say wrong the whole episode. So buckle on up. This is a new effort from the devs, Fabian Hiller.

He's behind ValleyBot. That's a JavaScript validation library. David Blass, he's behind a

relatively new validation library called Archtype and Colin

McDonald. We've had him on the podcast as well. He is a creator of Zod, TRPC. Basically,

all of these validation library authors sort of got together and put together this thing called

a standard schema. And today we're going to explain to you why and what that is and why this is good for you

as the end developer.

My name is Wes, developer from Canada with me as always is Scott.

How you doing today, Scott?

Doing good.

Just got back from the mountain.

I went skiing.

I went to the mountain to go skiing. I actually did.

Pimaing. Yeah. Yeah, I'm doing good, man. Just hanging out, doing some creative coding and having fun. I'm excited to learn about this stuff a little bit because I guess what I don't understand about this whole thing is why. I mean, I get that having a common interface amongst these libraries is

great if that's what this means. But in the same regard, then like, why not just collaborate

on those of the library itself? Yeah. Yeah, yeah, might not make that a standard library.

Yeah. But a large part about what these libraries are doing is oftentimes with data validation.

Data validation, one of those big things that like, hey, if you're not validating or parsing your data correctly, you might get some errors in your code.

Those errors, you might not know about them.

And unless they pop up in your century dashboard because you're seeing something of property

is undefined. And then all of a sudden, your users are having a bad time because maybe your data

...