Steve Tuck

But that just didn't happen for a variety of reasons.

That didn't happen.

So, I mean, Nutanix is, the problem, the challenge, and I don't want to disparage Nutanix, I would just say that just in terms of what Nutanix is, and they make a hypervisor, they make orchestration software around it, they have not done, have not engaged in hardware software code design.

Like that is,

That is just where they, you know, and initially you would buy, I think that they were endeavoring to label hardware.

But I think that at this point, it's kind of bring your own.

Then they've got a hardware compatibility list and it's all looks very familiar.

That's what we did at Joint, Stephen.

That's what we had the hardware.

Hard work compatibility listen you you only bring your own hardware and like you can do stuff like that but the reason we did oxide the way we did it is because We feel that you can't that there are problems at scale that you simply can't solve with that approach So I would say that Nutanix is taking it.

It just it's fundamentally a different approach.

And I think it is the, I probably was more fixated on just the risk elements of like the storms that, we can weather, I mean, quite literally any storm with this.

Would you say that out loud?

I'm cutting that from the podcast.

Nope, nope, nope.

I'm saying it out loud.

No, I'm saying it out loud and I'm not knocking on wood.

Wow, okay.

Okay, don't double down.

No, the gods.