Conrad Irwin

We have a dedicated... A dedicated team of volunteers. There's three or four people who I see regularly doing Windows fixes and ports. We need a breath after Linux before we dump into the next platform. But it is something we'd like to have. Windows is going to be fun for different reasons than Linux. Some of the same problems. It's a little bit more fragmented, though less so.

We have a dedicated... A dedicated team of volunteers. There's three or four people who I see regularly doing Windows fixes and ports. We need a breath after Linux before we dump into the next platform. But it is something we'd like to have. Windows is going to be fun for different reasons than Linux. Some of the same problems. It's a little bit more fragmented, though less so.

But the big one is the file path separator is the wrong way around. And we use Rust's path buff extensively internally. But if we allow collaboration between Linux and Windows, we can't represent a path in a path buff because it might be a Windows UTF-16 path or it might be a Linux UTF-8 path.

But the big one is the file path separator is the wrong way around. And we use Rust's path buff extensively internally. But if we allow collaboration between Linux and Windows, we can't represent a path in a path buff because it might be a Windows UTF-16 path or it might be a Linux UTF-8 path.

But the big one is the file path separator is the wrong way around. And we use Rust's path buff extensively internally. But if we allow collaboration between Linux and Windows, we can't represent a path in a path buff because it might be a Windows UTF-16 path or it might be a Linux UTF-8 path.

So we need some kind of new file path abstraction that is not tied to the current system, which is one of the downsides of the way Rust does that.

So we need some kind of new file path abstraction that is not tied to the current system, which is one of the downsides of the way Rust does that.

So we need some kind of new file path abstraction that is not tied to the current system, which is one of the downsides of the way Rust does that.

Cross-platform is a little manual, to be honest. So the way that the app is set up, you have kind of a platform-specific layer, and then everything else is Rust. We have a test implementation of the platform-specific layer, so we can very easily test all the stuff that's not platform-specific. And it mostly just works.

Cross-platform is a little manual, to be honest. So the way that the app is set up, you have kind of a platform-specific layer, and then everything else is Rust. We have a test implementation of the platform-specific layer, so we can very easily test all the stuff that's not platform-specific. And it mostly just works.

Cross-platform is a little manual, to be honest. So the way that the app is set up, you have kind of a platform-specific layer, and then everything else is Rust. We have a test implementation of the platform-specific layer, so we can very easily test all the stuff that's not platform-specific. And it mostly just works.

And sure, there are a couple of if statements that depend on what platform you're on, but mostly the code is the same for everyone. And that is one of the nice things about Rust. It is just Rust. When it comes to testing platform integrations, like back to keyboard shortcut handling, like when you type these keys on this keyboard layout on Mac OS, it should do this instead.

And sure, there are a couple of if statements that depend on what platform you're on, but mostly the code is the same for everyone. And that is one of the nice things about Rust. It is just Rust. When it comes to testing platform integrations, like back to keyboard shortcut handling, like when you type these keys on this keyboard layout on Mac OS, it should do this instead.

And sure, there are a couple of if statements that depend on what platform you're on, but mostly the code is the same for everyone. And that is one of the nice things about Rust. It is just Rust. When it comes to testing platform integrations, like back to keyboard shortcut handling, like when you type these keys on this keyboard layout on Mac OS, it should do this instead.

I have not figured out a better way than just getting yourself into that setup and trying it. And so to be determined.

I have not figured out a better way than just getting yourself into that setup and trying it. And so to be determined.

I have not figured out a better way than just getting yourself into that setup and trying it. And so to be determined.

pretty much integration tests for the most part. So we have, as you know, we have collaboration. And because the server piece is also written in Rust and also part of the same repository, we boot up the server, we boot up Zeds, and we talk through both of them. And so we have full integration tests. And I kind of like that approach because A, it lets you test interesting ordering properties.

pretty much integration tests for the most part. So we have, as you know, we have collaboration. And because the server piece is also written in Rust and also part of the same repository, we boot up the server, we boot up Zeds, and we talk through both of them. And so we have full integration tests. And I kind of like that approach because A, it lets you test interesting ordering properties.

pretty much integration tests for the most part. So we have, as you know, we have collaboration. And because the server piece is also written in Rust and also part of the same repository, we boot up the server, we boot up Zeds, and we talk through both of them. And so we have full integration tests. And I kind of like that approach because A, it lets you test interesting ordering properties.