.NET and Go are a weird pairing, especially since the library isn't actually "cross-platform." It's two separate implementations. I wonder what the impetus was to develop this library on those two particular platforms, especially since there's already Akka.NET and most people can't shut up about how much they love Goroutines as a concurrency primitive.
Proto Actor – Fast distributed actors for Golang and C#
11–20 of 47 posts
Re: Proto Actor – Fast distributed actors for Golang and C#
#12We should be really skeptical of (or perhaps we could charitably say, "We should contextualize these,") speed claims. Akka does well in benchmarks too, until you put significant memory pressure on the VM and find it handles less gracefully under load than a more JVM-natural approach using approaches in java.util.concurrent. Actor-based approaches with hundreds of thousands of actors are really amazing, powerful and o…
Take one or two features from Erlang into another language, and you have meh.
Re: Proto Actor – Fast distributed actors for Golang and C#
#13We should be really skeptical of (or perhaps we could charitably say, "We should contextualize these,") speed claims. Akka does well in benchmarks too, until you put significant memory pressure on the VM and find it handles less gracefully under load than a more JVM-natural approach using approaches in java.util.concurrent. Actor-based approaches with hundreds of thousands of actors are really amazing, powerful and o…
My favorite conference talk is about the multiple facets of Erlang that combine to make it such a great language. Take an opinionated language, an opinionated VM, and a focus on a specific problem space, and magic happens. Take one or two features from Erlang into another language, and you have meh.
But what doesn't work is trying to slavishly copy the Erlang/Pony style without those considerations.
Re: Proto Actor – Fast distributed actors for Golang and C#
#14I am interested and I will certainly read the Go version of the documentation, but the .NET of the docs are showing Go code instead. http://proto.actor/docs/dotnet/hello%20world
Re: Proto Actor – Fast distributed actors for Golang and C#
#15I am interested and I will certainly read the Go version of the documentation, but the .NET of the docs are showing Go code instead. http://proto.actor/docs/dotnet/hello%20world
Re: Proto Actor – Fast distributed actors for Golang and C#
#16We should be really skeptical of (or perhaps we could charitably say, "We should contextualize these,") speed claims. Akka does well in benchmarks too, until you put significant memory pressure on the VM and find it handles less gracefully under load than a more JVM-natural approach using approaches in java.util.concurrent. Actor-based approaches with hundreds of thousands of actors are really amazing, powerful and o…
My favorite conference talk is about the multiple facets of Erlang that combine to make it such a great language. Take an opinionated language, an opinionated VM, and a focus on a specific problem space, and magic happens. Take one or two features from Erlang into another language, and you have meh.
If that's what your domain space needs, use the BEAM and find a way to talk to it for the parts that you can't move to Erlang.
Re: Proto Actor – Fast distributed actors for Golang and C#
#17I am interested and I will certainly read the Go version of the documentation, but the .NET of the docs are showing Go code instead. http://proto.actor/docs/dotnet/hello%20world
And im getting bunch of 404s for .net docs. Which means its not really a serious project
Re: Proto Actor – Fast distributed actors for Golang and C#
#18We should be really skeptical of (or perhaps we could charitably say, "We should contextualize these,") speed claims. Akka does well in benchmarks too, until you put significant memory pressure on the VM and find it handles less gracefully under load than a more JVM-natural approach using approaches in java.util.concurrent. Actor-based approaches with hundreds of thousands of actors are really amazing, powerful and o…
>powerful and often simpler than equivalent channel based systems, conceptually
Without true experience with any of agents/channels, what make it simpler? I read the GO and compare with Actors in F# or Erlang and for me it easier to understand channels. Mainly because are typed on the data.
Re: Proto Actor – Fast distributed actors for Golang and C#
#19Most of my non trivial goroutines are organized like this: func actor_foo(things) error { set_up_stuff() defer clean_up_stuff() for { select { case msg := I recognize there is more to the actor model than just message loops, but I found that an explicit for-select-switch results in better overall readability.
Re: Proto Actor – Fast distributed actors for Golang and C#
#20Earlier quoted context omitted.
My favorite conference talk is about the multiple facets of Erlang that combine to make it such a great language. Take an opinionated language, an opinionated VM, and a focus on a specific problem space, and magic happens. Take one or two features from Erlang into another language, and you have meh.
Considering the production system that the Erlang VM has been deployed to(and the length of time it's existed and thrived) it's hard to make an argument to re-invent it in another language. If that's what your domain space needs, use the BEAM and find a way to talk to it for the parts that you can't move to Erlang.