Jeff Kao

And sort of similar with Golang, you know, like I think Golang was sort of evolved from Google, from like their large C++ monorepo.

And so like a lot of these like, you know, things that we, you know, I mentioned about like,

make programming enjoyable is, you know, things like mapping and filtering and like all of these sort of expressive aspects.

We felt like because we had a bit of a short timeline, it almost felt like a step back in terms of like the sort of the joy of programmer, like being able to express, especially concepts where

You have to process strings in very precise ways.

In a lot of ways, a lot of searches, if you ever do these leak code problems, there's so much string processing.

And having more expression really helps you to make the code very clear about some very potentially complicated ways that you process strings.

Right, right.

And so we saw... I think there's a very famous blog post.

If you go on Hacker News and look up Rust or migrating to Rust, I think the first result is always this one about Discord moving from Golang to Rust.

And so...

We, it almost sort of motivated us to see like, oh, they had occasional garbage collecting issues.

And even working at like other companies where we use Scala and the JVM, like there was consistently like issues with like the JVM and like the garbage collector.

And, you know, there's so much innovation around the garbage collector.

But we knew like for a lot of what we were doing, text processing and indexing, things like that, we're going to store large data structures just in memory.

I know there's these concepts of off-heat memory, but that's already sort of off the happy path of the language we're using.

So we're almost like...

putting a barrier or, like, something impeding us before we even got started.

So we really did want to have something where we had a lot more control over the memory.

But we also didn't want a language like C or C++ where you sort of have to expect developers to understand these, like, concepts.