Chris Lattner

Right.

And so now what that meant practically is that the push from launch to first of all, the fall, but then to 2.0 and 3.0 and like all the way forward was super painful for the engineering team.

and myself, it was very stressful.

The developer community was very grumpy about it because they're like, okay, well, wait a second, you're changing and breaking my code.

And like, we have to, to fix the bugs.

And it was just like a lot of tension and friction on all sides.

There's a lot of technical debt in the compiler because we have to run really fast and you have to go implement the thing and unblock the use case and do the thing.

And, and, you know, it's not right, but you'd never have time to go back and do it.

Right.

And I'm very proud of the Swift team because they've come

We, but they came so far and made so much progress over this time since launch.

It's pretty incredible.

And Swift is a very, very good thing.

But I just don't want to do that again, right?

And so what we're doing is we're not launching it when it's hopefully 0.9 with no testers.

We're launching it and saying it's 0.1, right?

And so we're setting expectations of saying like, okay, well, don't use this for production.

If you're interested in what we're doing, we'll do it in an open way and we can do it together, but don't use it in production yet.

We'll get there, but let's do it the right way.

And I'm also saying, we're not in a race.