jelly-actix-web-starter VS hyper

You can look at https://github.com/secretkeysio/jelly-actix-web-starter

My usual reminder that I have a Django-ish template for actix-web that I maintain: https://github.com/secretkeysio/jelly-actix-web-starter

Now that actix-web 4.0 is out I should be able to finally resolve one of the open issues/PRs, which I was waiting on 4.0 for.

For those interested in Django-in-Rust type approaches, I maintain an actix-web starter project that does exactly this: https://github.com/secretkeysio/jelly-actix-web-starter

I maintain a starter for all of this kind of stuff on top of actix-web, for anyone interested: https://github.com/secretkeysio/jelly-actix-web-starter/

Curious why you went with the mailbox approach - since a request is pretty much in-and-out, I found it sufficient to just write a trait for HttpRequest and have a custom render(...) method that pulls any flash messages from the session, thus clearing them. Wouldn't surprise me if I'm missing something tho.

I love Askama, but being tied to compile time changes is an absurd handicap on a web framework in the initial iteration phase. With Tera, you can implement a watcher for template changes and reload them without needing to recompile the entire framework.

If you want, I have an open source actix-web repo that does stuff like this for you already.

If you enjoy Python's web story but want something similar-ish in Rust, you can check out my actix boilerplate repo - it "mimics" Django in many ways. If nothing else, might be useful for picking apart.

> If you are equally picky and constrain yourself to parts of the ecosystem which care about binary size, you still have more options and can avoid size issues.

What's an example of this for, say, libcurl? On my system it has a tiny number of recursive dependencies, around a dozen. [0] Furthermore if I want to write a C program that uses libcurl I have to download zero bytes of data ... because it's a shared library that is already installed on my system, since so many programs already use it.

I don't really know the appropriate comparison for Rust. reqwest seems roughly comparable, but it's an HTTP client library, and not a general purpose network client like curl. Obviously curl can do a lot more. Even the list of direct dependencies for reqwest is quite long [1], and it's built on top of another http library [2] that has its own long list of dependencies, a list that includes tokio, no small library itself.

In terms of final binary size, the installed size of the curl package on my system, which includes both the command line tool and development dependencies for libcurl, is 1875.03 KiB.

[0] I'm excluding the dependency on the ca-certificates package, since this only provides the certificate chain for TLS and lots of programs rely on it.

[1] https://crates.io/crates/reqwest/0.11.24/dependencies

[2] https://crates.io/crates/hyper/0.14.28/dependencies

hyper-based HTTP server generating JSON responses. Written in Rust.

tokio / hyper / toml / serde / serde_json / json5 / console

Using Rust here was immensely helpful, using libraries made by the community like https://github.com/hyperium/hyper really powered up the development of Signway, so glad to see this kind of awesome crates made public. Hope that it continues to be like that despite the current controversies.

- Discord sends a slightly weird request by specifying content length (a bug in hyper we've not yet upgraded to fix, https://github.com/hyperium/hyper/commit/fb90d30c02d8f7cdc9a643597d5c4ca7a123f3dd)