Tide's Future Direction

[dbettin]

Question

What is the status of tide? It feels as if it might be dying. Which, if true, is unfortunate. It has some of the rust web framework ergonomics in addition to first-class async/await support.

Additional context

I am willing to help in anyway possible. My company has plans to use the fx via Google Cloud Run. But, I need to understand the overall direction of the project.

[yoshuawuyts]

@dbettin hi! -- thanks for reaching out. You're right that development on Tide has slowed down a bit recently, but for good reason!

We've been hard at work with building surf, an HTTP client counterpart to Tide. This allowed us to experiment with some new API directions. And more recently several Tide maintainers have been working on async-std, an async version of the standard library.

There's still a bit more work to do on the latter project. In particular I'm now working on building out a complete concurrency story, focusing on streams next.

This shouldn't be too long anymore though. My own goal is to work for a few more weeks on async-std, and then take the experience we've gather building surf + async-std and pick development back up on tide.

It's hard for me to judge whether you should pick Tide right now. Things are probably going to change again soon. But I figured I'd share the full context so you get to best decide. Hope this is helpful!

[tomhoule]

I've been very short on open source time in the past months, but I want to continue participating in the near future (possibly by making https://github.com/tomhoule/tide-static-files actually usable), it would be a shame if tide didn't materialize further! I'll be on the async ecosystem discord to try to contribute to the discussion.

[yoshuawuyts]

The road ahead

A quick update to what the plan currently is. The rustasync working group is coming to a close, which means Tide, Surf and related projects will need a new home. To that end I’ve created the http-rs org. I’ll be moving over Tide, Surf and related crates over tomorrow.

With async/await stabilization around the corner (9 days!) I’d like to take the chance to ramp work back up. This includes doing a full pass over the issue tracker, updating dependencies, and making a lot of changes we’ve put off for the past few months. In particular I’d like us to get into a releasable state. This means a period of active development, but my hope is that we’ll be able to convert it into a series of actionable items from there.

Thanks everyone for having been involved with Tide & the async ecosystem WG. I’m excited for what comes next!

[dvic]

Great news! I'm looking forward to contribute to Tide! For example, a while back I encountered http-rs/http-service#43 (comment), that might be something I could take a stab at (depending on the first list of actionable items).

Thanks for all the hard work 👍

[secretfader]

@yoshuawuyts Sounds positive, even if the news is a bit unexpected. Can existing members of @rustasync/maintainers get access to the new org(s)?

[prasannavl]

Now http-rs looks awfully similar to hyperium org. Wondering if it's worth exploring an opportunity for a merge under the http-rs umbrella, if that's beneficial to the ecosystem, esp. with projects like http, and h2 over there.

[yoshuawuyts]

@prasannavl I don't think merging with Hyperium is a likely option in the near future. For both technical and social reasons it's probably best if we go our separate ways for the time being.

@secretfader some maintainers have been invited to the org already. I had some trouble getting a hold of you in the past, which is why I didn't reach out about this beforehand.

In general I'd like to really dig into Tide for a bit, bringing it to a publishable state. This means focusing on technical work for a bit, land less so on management. We can and probably should revisit team membership in the future, but for now I'd like to punt that in favor of working on the project itself.