Sorry for the shameless self-plug, but hyper was actually a ton easier than I was expecting it would be, it's worth a try!
Actix is like Akka for Scala, it's a domain-agnostic implementation of the Actor model and I thought it was, you know, integral to how actix_web worked. While actors are a cool way to do concurrency, it was pretty boilerplate heavy - for instance, interfacing with a database in 0.7 meant defining an Actor specifically for the database that runs concurrently and having your handlers interact with that. It looks like this is all streamlined in 1.0, but I'm totally fuzzy on what the word "actix" means in this context now.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for the reply! Ya from my quick look it did definitely look like
Rocketwas using a lot of macros and stuff like that.Oh wow, that's interesting that it doesn't depend on
actixanymore lol. I don't know much about those projects but that's a fun fact!It turns out that article was already on my Reading List! Gotta be better about picking things off that list!
Sorry for the shameless self-plug, but
hyperwas actually a ton easier than I was expecting it would be, it's worth a try!Actix is like Akka for Scala, it's a domain-agnostic implementation of the Actor model and I thought it was, you know, integral to how
actix_webworked. While actors are a cool way to do concurrency, it was pretty boilerplate heavy - for instance, interfacing with a database in 0.7 meant defining an Actor specifically for the database that runs concurrently and having your handlers interact with that. It looks like this is all streamlined in 1.0, but I'm totally fuzzy on what the word "actix" means in this context now.