Ben Naecker

That's a great point, Ben. That's a great point because keep in mind the context here, which is customers bought this thing to host their data, like their virtual disks, their virtual instances. So we're like, actually, we thought maybe some of ours would.

That's a great point, Ben. That's a great point because keep in mind the context here, which is customers bought this thing to host their data, like their virtual disks, their virtual instances. So we're like, actually, we thought maybe some of ours would.

I don't know, we'd let users get half of what they paid for. I don't know, something like that seems fair. And then we'd take the rest.

I don't know, we'd let users get half of what they paid for. I don't know, something like that seems fair. And then we'd take the rest.

Well, that may also be reflective of a little confusion. ClickHouse is not hosted in Crucible. So we're doing replication through ClickHouse's own mechanisms, whereas Crucible is what we use to store the data associated with instance data, like the customer's virtual volumes. That's what Crucible is for.

Well, that may also be reflective of a little confusion. ClickHouse is not hosted in Crucible. So we're doing replication through ClickHouse's own mechanisms, whereas Crucible is what we use to store the data associated with instance data, like the customer's virtual volumes. That's what Crucible is for.

And so we're using those same U.2 devices, both for Crucible volumes and for ClickHouse, but they're pretty much separate concerns.

And so we're using those same U.2 devices, both for Crucible volumes and for ClickHouse, but they're pretty much separate concerns.

No, no. Can't imagine storing it. Can't imagine querying it. Just, they're wrong.

No, no. Can't imagine storing it. Can't imagine querying it. Just, they're wrong.

And you're going to bring up Antler. Yeah, absolutely.

And you're going to bring up Antler. Yeah, absolutely.

Antler lover when I was doing stuff in Java. That's been a minute, but thanks for exposing me. Thanks for outing me as a former Java expat or whatever. I knew you loved Antler more than Java. Oh, 100%. Yeah, no, I think Antler is terrific. Never loved Java, but did love Antler. But Ben, didn't we use PEG? Or maybe was it PEST in the USDT stuff?

Antler lover when I was doing stuff in Java. That's been a minute, but thanks for exposing me. Thanks for outing me as a former Java expat or whatever. I knew you loved Antler more than Java. Oh, 100%. Yeah, no, I think Antler is terrific. Never loved Java, but did love Antler. But Ben, didn't we use PEG? Or maybe was it PEST in the USDT stuff?

So, Brian, I'm glad you brought up Antler because I feel like Antler was very domain-specific to Java. And to bring us back to the beginning, it seems like these other systems are much more native for Rust. I mean, for example, there is an Antler generation for Rust. And I haven't kept tabs on the state of it.

So, Brian, I'm glad you brought up Antler because I feel like Antler was very domain-specific to Java. And to bring us back to the beginning, it seems like these other systems are much more native for Rust. I mean, for example, there is an Antler generation for Rust. And I haven't kept tabs on the state of it.

But it makes sense to have a domain-specific language for this kind of activity specific to the language that you want to use to augment that generation.

But it makes sense to have a domain-specific language for this kind of activity specific to the language that you want to use to augment that generation.

For like, you don't want to have the least common denominator. Turns out domain-specific languages can be valid. I'm sure there are lots of them that shouldn't have been written or whatever. But as long as you're looking at the available options and considering the aspects of the domain.

For like, you don't want to have the least common denominator. Turns out domain-specific languages can be valid. I'm sure there are lots of them that shouldn't have been written or whatever. But as long as you're looking at the available options and considering the aspects of the domain.