async programming in scala, are futures the standard now?
does this broadly look correct, im implementing a grpc server and i dont see why i shouldn't use futures as my primary concurrency model for async programming, they are fairly simple, i come from a go background and i dont see the value in trying to do as complex as create a whole framework of actors. im assuming the async execution contexts are managed by
Http().newServerAt and i dont really need to do more than write my logic1 Reply
⌛ This post has been reserved for your question.
Hey @mmacheerpuppy! Please useTIP: Narrow down your issue to simple and precise questions to maximize the chance that others will reply in here./closeor theClose Postbutton above when your problem is solved. Please remember to follow the help guidelines. This post will be automatically marked as dormant after 300 minutes of inactivity.
💤 Post marked as dormant
This post has been inactive for over 300 minutes, thus, it has been archived.
If your question was not answered yet, feel free to re-open this post or create a new one.
In case your post is not getting any attention, you can try to use /help ping.
Warning: abusing this will result in moderative actions taken against you.