Yeah. It looks like it's under progress, I'm really excited for HTTP futures as well. It will make it exceptionally easy to build highly performant web servers.
It would be so great if Sean got to work full time on hyper, but of course I understand that he is needed elsewhere at Mozilla and he's doing a great job with the time he has. I would hazard a guess that there are so many besides me waiting for the upcoming HTTP client/server improvements that it would probably not be the worst idea if Mozilla (or some other org betting on Rust) threw some money at it.
I'm extremely grateful to everyone working on Rust and its ecosystem (paid or otherwise) for the work that you do. It sure sounds cheesy, but after trying lots of stuff over the years, Rust feels like coming home. There, I said it. I'm pushing it at my employer, and for every piece of tooling or important crate that matures, it gets easier to evangelize.
Yeah, I hear you. That said, money is being thrown, but at tokio itself, rather than at hyper. You have to finish the lower bits before the higher ones.
I'm in a lucky position to be able to choose the tools I use at work. For certain parts, Rust's been already a great help and right now I wait tokio and hyper/tokio more than I waited for Super Nintendo when I was a child. They will be an enormous help when refactoring the current services. I'm pushing myself to learn more so I could be helping with these projects.
That said, thank you for the whole Rust team. It hits the sweet spot being fast, not eating so much memory, being pleasure to write and having amazing tooling around it.
Sean (or other Hyper maintainers), if you're reading this, it'd be really useful to have a tracking issue for the Tokio integration rather than just a branch. I'd like to be able to subscribe to something to keep track of progress and discussion on the topic!
