Conrad Irwin

Yeah, I mean, I definitely see the problem, given the examples that we have. So one of the things that I'm hopeful for is that as the language evolves, you know, AsyncRust is still very beta, as I think they called it in the latest Rust planning blog post.

Yeah, I mean, I definitely see the problem, given the examples that we have. So one of the things that I'm hopeful for is that as the language evolves, you know, AsyncRust is still very beta, as I think they called it in the latest Rust planning blog post.

As they evolve the language support for it, what I hope is that it becomes easier to do both sides of things, both easier to use as a consumer, but also easier to create as a kind of like, hey, here's my new Async library for you.

As they evolve the language support for it, what I hope is that it becomes easier to do both sides of things, both easier to use as a consumer, but also easier to create as a kind of like, hey, here's my new Async library for you.

As they evolve the language support for it, what I hope is that it becomes easier to do both sides of things, both easier to use as a consumer, but also easier to create as a kind of like, hey, here's my new Async library for you.

And I think if you look at something like jQuery to use a very different example, it was something that started out very dominant or started out small, became very dominant very quickly. And then as the underlying browser APIs improved, became kind of less relevant.

And I think if you look at something like jQuery to use a very different example, it was something that started out very dominant or started out small, became very dominant very quickly. And then as the underlying browser APIs improved, became kind of less relevant.

And I think if you look at something like jQuery to use a very different example, it was something that started out very dominant or started out small, became very dominant very quickly. And then as the underlying browser APIs improved, became kind of less relevant.

So that's kind of the hope I'd see, if that makes sense, of as the APIs get more sensible and people get more used to all of the concepts involved, it becomes easier to do both sides of the coin. So I have nothing against Tokyo. It's a great piece of software. But I also, to your point earlier, I really like the diversity of being able to do things in multiple different ways.

So that's kind of the hope I'd see, if that makes sense, of as the APIs get more sensible and people get more used to all of the concepts involved, it becomes easier to do both sides of the coin. So I have nothing against Tokyo. It's a great piece of software. But I also, to your point earlier, I really like the diversity of being able to do things in multiple different ways.

So that's kind of the hope I'd see, if that makes sense, of as the APIs get more sensible and people get more used to all of the concepts involved, it becomes easier to do both sides of the coin. So I have nothing against Tokyo. It's a great piece of software. But I also, to your point earlier, I really like the diversity of being able to do things in multiple different ways.

But even things like async traits and stuff like that, there's so much obvious stuff that needs improvement first that I think there's definitely time to figure it out, even if it feels like it's not figured out yet. Come on. What percentage of Z is async? I would guess 50-50, but I don't know. Here we could have a look. But pretty much everything that requires accessing the disk is async.

But even things like async traits and stuff like that, there's so much obvious stuff that needs improvement first that I think there's definitely time to figure it out, even if it feels like it's not figured out yet. Come on. What percentage of Z is async? I would guess 50-50, but I don't know. Here we could have a look. But pretty much everything that requires accessing the disk is async.

But even things like async traits and stuff like that, there's so much obvious stuff that needs improvement first that I think there's definitely time to figure it out, even if it feels like it's not figured out yet. Come on. What percentage of Z is async? I would guess 50-50, but I don't know. Here we could have a look. But pretty much everything that requires accessing the disk is async.

The network is async, and text editors do a lot of disk access and lots of language server access. And so the stuff that's not async is really just, oh, you typed a key? Okay, left. One move the cursor one position to the left. We can do that synchronously.

The network is async, and text editors do a lot of disk access and lots of language server access. And so the stuff that's not async is really just, oh, you typed a key? Okay, left. One move the cursor one position to the left. We can do that synchronously.

The network is async, and text editors do a lot of disk access and lots of language server access. And so the stuff that's not async is really just, oh, you typed a key? Okay, left. One move the cursor one position to the left. We can do that synchronously.

But even things like search, if you search for a character, we kick that off to an async background thread so that we can keep rendering UI while we search. And so... Pretty much anything that uses a lot of CPU is not on the main thread.

But even things like search, if you search for a character, we kick that off to an async background thread so that we can keep rendering UI while we search. And so... Pretty much anything that uses a lot of CPU is not on the main thread.

But even things like search, if you search for a character, we kick that off to an async background thread so that we can keep rendering UI while we search. And so... Pretty much anything that uses a lot of CPU is not on the main thread.