actix-web

I'm unifying Rust's async HTTP implementations H1, H2, H3 and Google's tarpc in Rust~Actix~Torchbear. I just don't have a lot of time now sice my house got broken and I don't have enough money to rent anywhere. It also needs a lot of work on the parsing layer, and the laptops with my notes on them are hard to keep with me as I move around. https://github.com/google/tarpc https://github.com/actix/actix-web/tree/master/actix-http/sr... https://github.com/hyperium/h2 https://github.com/djc/quinn/tree/main/quinn-h3 https://github.com/speakeasy-engine/torchbear/blob/master/sr... ~ There's beauty in this with the fluency in which complex applications like the coming secure social network, Radiojade, are built. See this example: !# https://github.com/foundpatternscellar/ping-pong/blob/master... Curl users, do you really want to stick with Bash'

For Rust, I am using Actix https://github.com/actix/actix-web . Without better definition of "secure" and "performance" there is no way to help you. Both of them are used and exposed publicly by numerous companies, so ootb they good enough for any API. For 99.999% percent of people both are performant enough. Rust will win on memory usage, in some cases significantly, and will win on performance by a smaller margin, but run your own benchmark. This is an interesting article about why npm uses Rust instead of something else: https://www.infoq.com/news/2019/03/rust-npm-performance/ >performance of the framework is very important No, its not. Whatever you do with it, will be 100-1000x slower than what framework does. Making decision on something that takes 0.01% of time spend on request handling makes no sense. Optimize your code and data so

Direct link to repo: https://github.com/actix/actix-web

I used rocket (https://rocket.rs) mostly because at the time (Nov '19) it seemed to be the one with by far the best documentation. I think that these days, I would probably go with actix (https://github.com/actix/actix-web), because rocket does not appear to me as being actively maintained and not having async support (yet? there is a branch..) means I need workarounds to integrate with libraries that are async only. But still, rocket is pretty great. Implementing an endpoint is as simple as a few lines and great integration with serde as well as diesel means you can integrate pretty quickly.

Not true, he passed the reins: https://github.com/actix/actix-web/issues/1289

With actions taken in all of 5 issues. See all issues here https://github.com/actix/actix-web/issues?q=label%3Aunsafe+

The project seems active: https://github.com/actix/actix-web

That seems a pretty balanced summary from my understanding of it. One thing that I think should be noted: a lot has been said about this framing the original developer as unwilling. I'd say an unfair amount - from what I've seen, "cautiousness" would be a better description of his attitude, and hostility seems to have been shown when people blindly wade in ignoring all the discussion. So for example, back in 2018, here he is publicly mulling it over: https://github.com/actix/actix-web/issues/289#issuecomment-3... and https://github.com/actix/actix-web/issues/289#issuecomment-3... Here he is actively working to reduce the reliance on unsafe practices: https://github.com/actix/actix-web/issues/289#issuecomment-3... Here he actively and very concisely points out his actual viewpoint: https://github.com/actix/actix-web/issues/289#issuecomment

This framework's core developer has left, probably new community took it over. Hopefully it will continue to be supported and developed. Rust still has a way to go for being a mature eco-system for doing any serious web programming work. Given the focus of Rust on systems programming, I will still be careful to consider it for anything web related. Hopefully situations like abandoning a project suddenly will not happen again. [1] [2] [1] https://words.steveklabnik.com/a-sad-day-for-rust [2] https://github.com/actix/actix-web/issues/1289

The project has a new leader now: https://github.com/actix/actix-web/issues/1289

At present Rust's primary focus is systems programming language, it will take another 3-5 years to be a viable web programming that too in a niche area. I doubt the libraries will be mature enough to provide easy way to build the way other languages do. If you know Ruby or Python or C# or Swift or Go language or Dart or TypeScript or JavaScript don't change to Rust yet. It's far far away from having similar library, documentation and developer eco-system. I believe Haskell has more mature web development eco-system than Rust at present, but they also suffer from same issue most libraries do not have enough documentation and it's tiring to go through the library code to understand how to use it. But if you want to do Rust, why not try Haskell, you will learn much more and it offers a new way of functional programming. Indeed Rust, Swift, C

Agreed. One could argue that a level of drama in the community is a sign of growing maturity and wider interest in the language, because it is evidence there is no longer a niche monoculture of devs all thinking the same way. In the words of Steve Klabnik "Rust has been an experiment in community building as much as an experiment in language building. Can we reject the idea of a BDFL? Can we include as many people as possible? Can we be welcoming to folks who historically have not had great representation in open source? Can we reject contempt culture? Can we be inclusive of beginners?" https://words.steveklabnik.com/a-sad-day-for-rust The Actix issue was resolved, and Actix will continue under new maintainers (https://github.com/actix/actix-web/issues/1289). So I'd argue the answer to those questions is a 'yes'.

The owner relented, and passed control to a contributor. It was on HN, but I found it easier to find the OP: https://github.com/actix/actix-web/issues/1289 Edit: discussed here: https://news.ycombinator.com/item?id=22099335

Yes, the creator of actix-web has appointed a new maintainer after realising it was unfair to just up and delete it. The issue is here: https://github.com/actix/actix-web/issues/1289 The project future is obviously in flux with this transition, but I am hoping myself & other contributors will be able to carve a path forward.