-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thank you for this new release
In the future, do you plan to rid of tokio by using http-service-anotherthing? Because using this tide release made us compile tokio and async_std, that’s quite a lot 
-
Oh yeah we definitely are looking to trimming the dependency tree down to only include what's truly needed. Already took some steps here, we used to compile the complete Iron framework too, but we can and should do much better!
- 2 more replies
New conversation -
-
-
that's like a 6 loc hello world, that's like express/koa, except this produces a single independent binary

-
Hehe, yes exactly! Mideware is super similar to Koa also. The biggest way in which we're diverging is that we aim to make Tide feature-complete with good defaults, while Koa/Express only provided the bare essentials.
End of conversation
New conversation -
-
-
Already in bed, so can't make a cool code preview. But check out the redirect API! It's so nice and easy! https://docs.rs/tide/0.4.0/tide/fn.redirect.html … Thanks to
@hoodie_de for helping out with this!Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Was so excited that the article seemed to imply middleware returns `Result<Response>`. That was one of the biggest changes I wanted to do an RFC on, but couldn't find the time. But looks like this is just `Response` from the docs. Could you please clarify?
-
We have a conversion from Result to Response implemented through IntoResponse. But this is a bit hard to enable right now. Like I said: error handling needs work

- 2 more replies
New conversation -
-
-
Does it work in stable rust or nightly?
-
Stable!
- 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.