Mitchell Hashimoto

I knew Go wouldn't be a choice because I knew I wanted to do something that really, I owned every single allocation and every single instruction that would ever be run. And having an active runtime that was running was never going to be, and a garbage collector was never going to be an option. The real plausible option there was Rust.

I knew Go wouldn't be a choice because I knew I wanted to do something that really, I owned every single allocation and every single instruction that would ever be run. And having an active runtime that was running was never going to be, and a garbage collector was never going to be an option. The real plausible option there was Rust.

And I didn't try it with the terminal because by then I had already had enough experience with Rust that I knew I didn't want to write Rust every day. The way I describe it is I philosophically and as a technical achievement, I have absolutely nothing but respect and I'm impressed by Rust. I think it's very impressive. But as a personal basis, it's very superficial.

And I didn't try it with the terminal because by then I had already had enough experience with Rust that I knew I didn't want to write Rust every day. The way I describe it is I philosophically and as a technical achievement, I have absolutely nothing but respect and I'm impressed by Rust. I think it's very impressive. But as a personal basis, it's very superficial.

When I write and read Rust, I'm not having fun. And I want to have fun. And part of the joy is writing the code. And, you know, it's very much a stylistic choice. I hate to put it in that perspective, because I think engineers want some sort of concrete objective reason of why one versus another is better. It's really a vanilla versus strawberry ice cream flavor sort of thing for me.

When I write and read Rust, I'm not having fun. And I want to have fun. And part of the joy is writing the code. And, you know, it's very much a stylistic choice. I hate to put it in that perspective, because I think engineers want some sort of concrete objective reason of why one versus another is better. It's really a vanilla versus strawberry ice cream flavor sort of thing for me.

It's they're both great. They both are edible, you know, but I, but I choose one over the other. And, um, that's, that's really what it came down to for me.

It's they're both great. They both are edible, you know, but I, but I choose one over the other. And, um, that's, that's really what it came down to for me.

I think so. I think so. And I think Andrew and people on the project would say the same thing. So, I mean, very directly before the project, I literally contributed to the compiler. So there's that very direct personal relationship. But with the project, I mean, Zig's still such a new versioning language that there aren't very many real-world users.

I think so. I think so. And I think Andrew and people on the project would say the same thing. So, I mean, very directly before the project, I literally contributed to the compiler. So there's that very direct personal relationship. But with the project, I mean, Zig's still such a new versioning language that there aren't very many real-world users.

And I think having this real-world use case exposed a lot of... not just bugs, but ergonomic improvements and issues. You know, one of the things that I think a very big thing, a couple of very big things that popped up really immediately was the need for package management and then beyond that, which is now sort of solved and within Zig, and beyond that, the need to enable packages

And I think having this real-world use case exposed a lot of... not just bugs, but ergonomic improvements and issues. You know, one of the things that I think a very big thing, a couple of very big things that popped up really immediately was the need for package management and then beyond that, which is now sort of solved and within Zig, and beyond that, the need to enable packages

system packagers, which are separate, like, you know, one of the things I'm doing with ghosty is I'm not doing any of the packaging, I'm going to release the source, I'm going to do the Mac app, because that's kind of you need to like kind of pay and sign in, blah, blah, blah. But all the Linux stuff, if you want to Ubuntu app package, or RPM, or Nix package, like I'm not doing any of that.

system packagers, which are separate, like, you know, one of the things I'm doing with ghosty is I'm not doing any of the packaging, I'm going to release the source, I'm going to do the Mac app, because that's kind of you need to like kind of pay and sign in, blah, blah, blah. But all the Linux stuff, if you want to Ubuntu app package, or RPM, or Nix package, like I'm not doing any of that.

And that's pretty classic, right? Like open source, like packagers are other people, you But Zig is such a new thing that I knew that would be challenging for those people.

And that's pretty classic, right? Like open source, like packagers are other people, you But Zig is such a new thing that I knew that would be challenging for those people.

And so Andrew did a really great job of listening to my feedback, but other real world projects and building in the system packaging mode and guidelines into Zig where I feel pretty good about when we go public that we're going to be in a place where

And so Andrew did a really great job of listening to my feedback, but other real world projects and building in the system packaging mode and guidelines into Zig where I feel pretty good about when we go public that we're going to be in a place where

hopefully ghosty pops into debian repos and stuff pretty quickly but that that's i think a good example of how things go um and then just compiler stability i mean the zig compiler moves super fast and i'll regularly just say ghosty doesn't compile anymore not because you made a breaking change but because like something's actually broken and i believe they use ghosty here and there as sort of a canary of whether the compiler is stable like can ghosty build and run

hopefully ghosty pops into debian repos and stuff pretty quickly but that that's i think a good example of how things go um and then just compiler stability i mean the zig compiler moves super fast and i'll regularly just say ghosty doesn't compile anymore not because you made a breaking change but because like something's actually broken and i believe they use ghosty here and there as sort of a canary of whether the compiler is stable like can ghosty build and run