I understand that using Actix really highlights the speed advantage of Rust... but I think it's irresponsible to encourage rewrites in Rust using a framework that's dead because the developer decided to quit instead of fix security issues[0]. The last thing we need is a bunch of new Rust devs rewriting their perfectly fine Node code using an insecure framework.
Rust is really fast, especially compared to Node. This is an easy benchmark to win. So why not use a framework that's actually secure.
It's the only web framework in Rust that has thus far reached maintenance mode because it became feature complete, was heavily vetted by many teams, and is architecturally mature. It's not just really fast but has all of the bells and whistles. Further, people are actively contributing to the project. Replacing remaining sound yet unsafe blocks with fully safe rust, without taxing performance, is the remaining, ongoing effort at hand.
Your claims about being dead are wildly exaggerated and misleading.
You're in NYC as am I. The Rust NYC meet-up is a great way to connect and learn more.
> Your claims about being dead are wildly exaggerated and misleading.
I’d say they’re outdated. The project after the original author was frustrated with some in the community, found a way to allow the project to continue, which is overall good, but still a very disappointing episode.
Yes, indeed, but calling it dead and accusing the OP of acting irresponsible requires attention.
What happened to Nikolay could happen to anyone who stands up for one's craftsmanship and refuses to change out of principle. You, or anyone, can wind up being targeted.
I agree. I wanted to make sure it was clear why people might have the misunderstanding that the project development isn’t continuing. I think it’s worth directly correcting that perspective.
Express.js active development seems to stop. The last commit on v5 branch was from October 2018. We are still waiting for http2 (2 years) or better support for promises (3 years).
Koa is great and makes the two obvious improvements to Express: first-class promises, and bubbling up a representation of the response instead of having your routes directly send the response. So you now have middleware instead of just Express' "beforeware".
If it is a small project I'd recommend just using the built in http server. It is what all these projects use anyway, and if it's just a few routes it's usually easier to just use that instead of pulling in more dependencies.
Yes, it is active with many recent contributions. The goal was to show how much opportunity is there for making things more optimal from running perspective. Imagine how much of cpu power and electricity wasted
Rust is really fast, especially compared to Node. This is an easy benchmark to win. So why not use a framework that's actually secure.
0. https://news.ycombinator.com/item?id=22073908