Actix: a small, pragmatic, and fast Rust web framework
61–70 of 125 posts
Re: Actix: a small, pragmatic, and fast Rust web framework
#62Re: Actix: a small, pragmatic, and fast Rust web framework
#63I tried using actix for a recent project. I just could not get it to do what I wanted to. It always felt like a fight. I switched to rocket and everything is so much easier. Everyone is saying great things about it, but I just want to point out that it's not for everyone.
Doesn’t Rocket dependend on nightly Rust? Doesn’t it use features that may never make it into stable Rust?
Re: Actix: a small, pragmatic, and fast Rust web framework
#64Earlier quoted context omitted.
Yes, I'm not constrained in any way to not be able to run a 5 MB binary. I was curious if that was an indication of what is to come for large projects... I guess I was tangentially pointing to complexity and abstraction there.
rust doesn't use dynamic linking, which contributes a lot to that size.
Re: Actix: a small, pragmatic, and fast Rust web framework
#65Re: Actix: a small, pragmatic, and fast Rust web framework
#66Earlier quoted context omitted.
To supplement the other sibling question that I answered: It's a learning experience. Right now, I can't port everything to Rust, because each platform has its advantages. Rust is still missing a lot of libs that exist in NPM and Maven, so it makes it difficult. I've been exploring exposing some functions that exist in Java/Kotlin through gRPC (as everything runs on the same network anyways) until it's available on R…
Of the libs that are missing in Rust, which one would you find the most useful? I'm looking for project ideas to get stuck into.. :)
Re: Actix: a small, pragmatic, and fast Rust web framework
#67I tried using actix for a recent project. I just could not get it to do what I wanted to. It always felt like a fight. I switched to rocket and everything is so much easier. Everyone is saying great things about it, but I just want to point out that it's not for everyone.
Just to clarify for others, Actix is a more general actor-based programming framework. Actix-web is a nice little web server framework built on top of that, which you could integrate with other Actix components. From looking at the two, Actix is more minimalist with direct control, though it has some nice middleware built in. Rocket is a more Rails-like “everything works and is magic” approach. Both seem like they co…
So as a result I've opted to using D instead for my current project, I've been able to get more figured out with Vibe.d in shorter time so I'll likely stick to D for this project due to time being a factor against me.
Re: Actix: a small, pragmatic, and fast Rust web framework
#68What a great looking site. I've been really exciting about actix for a while now. We just started some internal experiments with it here and I'm looking forward to more.
Agreed. Good site. This is an aside, and I sincerely apologize for that, but I am compelled... I'm reading the greeting/hello-world example on this nice site and I notice unwrap_or(). That is a poor name: can it panic, as suggested by the "unwrap" part (I have just enough Rust to know that,) or can it not, as suggested by the "or" part? The name is inherently ambiguous! It's as if the .unwrap() that is festooned thro…
Re: Actix: a small, pragmatic, and fast Rust web framework
#69Re: Actix: a small, pragmatic, and fast Rust web framework
#70Earlier quoted context omitted.
same question, why moved from Kotlin to Rust all the way.
To supplement the other sibling question that I answered: It's a learning experience. Right now, I can't port everything to Rust, because each platform has its advantages. Rust is still missing a lot of libs that exist in NPM and Maven, so it makes it difficult. I've been exploring exposing some functions that exist in Java/Kotlin through gRPC (as everything runs on the same network anyways) until it's available on R…