1036: Cursor & OpenAI Break Up

TJ (0:00)

Welcome to Syntax. Welcome to Syntax Weekly, the place with all your latest web dev programming news. We got a good one for you today. We're talking about how Cursor and OpenAI have broken up. Also, PMPM 12 has been released and it's been rewritten in Rust. There's also a cool web GPU library for agents.

All of this and more today on Syntax Weekly, I am joined by Wes Bos and Scott Tolinski. What's up? How are you guys doing?

Scott Tolinski (0:27)

Oh, I'm doing good. How are you doing, TJ.?

TJ (0:29)

I'm doing good. Let's get right into it. So, our first story today is the PMPM 12 release.

And so, this is a rewrite of PMPM in Rust and it's stable. And the one nice thing about it is it's not meant to be a migration. There's not a lot of major breaking changes. Things are just going to be faster and there's some cool sensible defaults as well. One of the first ones is project aware global bins. So, a lot of times you might have no Dino or BUN installed globally, but in any given project, you want to use a specific version of it. Now, when you're using PMPM, it'll look at the dev-engines.run time in your package.json and automatically choose to run the right version when you do a PMPM run.

Wes Bos (1:15)

That was a feature of Vite Plus that I've been very much enjoying.

TJ (1:20)

Yeah. So, it's here in PMPM. They also have Git dependency resolution.

There's so many different ways to install a package from GitHub. You could do username slash package, GitHub colon username slash package, and the SSH URL, the HTTPS URL. Now this normalizes it into a specific thing that shows up in your package.json, and then they have a resolution algorithm that'll, I believe it uses HTTPS to pull in that particular library or that particular commit. So, that's nice to see, a couple of other things.

Wes Bos (1:56)

I love how rewriting this in Rust is just like a half a sentence.

TJ (2:01)

Yeah, I was hoping to see stats like, is it faster? I mean, obviously it's faster, but also PNPM is fast. I've been using PNPM for like two years now because it's so much faster than NPM.

Scott Tolinski (2:14)

How do you get it faster? This is how I guess. I don't know.

Wes Bos (2:17)

It's not a problem I had had had, but maybe maybe it's even faster. That's unbelievable.

TJ (2:24)

Yeah.

Scott Tolinski (2:25)

Yes. PNPM. Another one.

TJ (2:27)

PNPM.

Scott Tolinski (2:28)

Yeah. PNPM. It's constantly pushing it, constantly evolving. And really, what would we what would we do without PNPM? It's the best folks.

TJ (2:36)

It's good stuff. Yeah. Check out their release post upgrade if you haven't yet. Check it out. I got one more release for you as well. And this is from the Zod team. So Zod has released version 4.5 and the big standout feature here is Schema Compilation. So they released a new method, z.compile. And this takes any schema into a pre-compiled schema that's three to nine times faster. And that compiled schema can be used in exactly the same way as any of your Zod validators.

It essentially just does it ahead of time. And so you can check out their their release post that shows up to 7.8 times faster when compiled. Cool.

There's a few other things in the 4.5 release. You can see their blog post here that talk about it. And then they have a specific post talking about z.compile. And essentially what they do, if you're not familiar, Zod validators were essentially like runtime validation, where when you did z.parse, it would actually have to go through and dynamically pick out all of those validators, dynamically invoke them. But the compilation essentially just creates a really quick, really fast bit of code that does that specific validation. And that's why it's so much faster. And so I believe they have like a VEEP plugin. There's a way to get it to run with Node.js, where these compiled schemas can actually be part of your bundle as well. So you don't even have the runtime cost of having to spin up this validator and do all the dynamic instantiation.

It's essentially just code. Like if type input does not equal object or input equals null, return false, or if type of input.x does not equal number, return false. So the kind of stuff that would be under the hood, but it basically does that ahead of time, so all of your runs for Zod parsing are going to be a lot faster. Basically, you just have to import Zod-compile, and now you're opted in and all of your Zod parsers are going to be a whole, Zod parsing is going to be a whole lot faster.