examples

actix-web seems really interesting, just from some cursory reading. Also, from a performance standpoint, it seems to be _really_ good: https://www.techempower.com/benchmarks/ This example in particular piqued my interest: https://github.com/actix/examples/blob/master/async_pg/src/m... I have no experience in Rust whatsoever, but I feel inspired to try it out.

An experienced Rust programmer will write generally better solutions in roughly the same amount of time as what is taken to write a solution in NodeJS, where the work is familiar. There is absolutely more code to write for a language where you can have fine control over practically everything, as long as it's within the constraints governing the compiler. However, web development consists of well-treaded paths using familiar patterns of data access and manipulation. If a new project does not benefit by code re-use, the experienced Rust programmer is going to have to use more tools and techniques to accomplish something similar in functionality to that created in other languages, but with far more guarantees and control. Who cares about guarantees and control? The team that is going to have to share the burden of maintaining the code

Hi @Dowwie, I'm one of those "others" you mentioned that's trying to fill Nikolay's very large shoes! Yuki (John Titor on GitHub), Rob and I are well on our way removing concerning `unsafe`s wherever we can. Sadly, there are some breaking changes but that's not stopping us and we're now headed to a 3.x release. No timeline on that just yet. The community has bounced back quite a bit ever since the transition and I'm hopeful that actix-web will continue to be the leader-ish of Rust web development! Just the other day we even had the first example mix some async_std into the mix (obviously, yes, some runtime weirdness with this)! https://github.com/actix/examples/tree/master/multipart-asyn... Happy to answer any questions y'all might have!

> You are saying that by uploading a library that works well, and whose presentation (docs, etc) are high quality ("professional") that the owner now has the responsibility to publicly state whether this is a personal project or not, and they must state their SLA and process with respect to accepting patches? No, I'm not. I'm saying if you setup an open source project framed as a project that is production ready & open to patches with a guise of being run by an organization and intentions of having a community, then it is reasonable to expect that you actually do that. You don't accidentally make a github organization, after all. There are community norms around what you can expect when working with such projects. Particularly when then both the github page and the webpage speak of being welcome to contributions ( https://github.com/actix

> If you offer code to the public – and present it as an active, dependable project – professional behavior is exactly what you implicitly promise and signed up for. If you can’t offer that (at any time, and for any reason), then you should immediately make that clear, front-and-center, to any current and future users. As far as I can tell, this project was released under the Apache License 2.0. https://github.com/actix/examples/blob/master/LICENSE Clause 7 of said license says the following: "7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHA

Actix-web actually makes things a little bit easier. Here is their "Hello World" example https://github.com/actix/examples/blob/master/hello-world/sr... The HTTP Handler (the index function) returns some plaintext and prints to the server's console. Removing the print makes the function simpler than the one in the main article. Actix Web was designed from the get-go to be a highly concurrent HTTP framework, and I think it is the most mature Rust web framework. Of course, the boilerplate main still needs to be written, and the way it does things is a bit more profound. But at a high level, I believe it is quite clear that it is handling logging, URL routing and connecting to a port.

I can second the suggestion for actix-web, it is a joy to use and I believe it is the only HTTP framework that has reached version 1.0 :) Have a look at the sort of things you can do with it https://github.com/actix/examples

https://github.com/actix/examples Hope this helps!

Anyone know why the super simple Middleware trait[1] was replaced by the more complex (and confusing at first) Transform and Service traits? Here's the simple middleware examples: 0.7: https://github.com/actix/examples/blob/0.7/middleware/src/si... 1.0: https://github.com/actix/examples/blob/master/middleware/src... Could a simple Middleware trait be added that would implement both new traits for us? [1]: actix_web::middleware::Middleware

That's nice and all. But then you have abominations like this: state .db .send(Queries::GetTopTenHottestYears) .from_err() .and_then(move |res| { result.push(res.unwrap()); state .db .send(Queries::GetTopTenColdestYears) .from_err() .and_then(move |res| { result.push(res.unwrap()); state .db .send(Queries::GetTopTenHottestMonths) .from_err() .and_then(move |res| { result.push(res.unwrap()); state .db .send(Queries::GetTopTenColdestMonths)