(just kidding, it was not a pleasant experience :p )
honestly, they're pretty fun!
randomly deciding to annihilate or delay a packet and seeing how the cluster reacts is pretty neat
@rogeralsing looks like they rewrote
Ask<> support in cannonical Akka: https://github.com/akka/akka/blob/master/akka-actor/src/main/scala/akka/pattern/AskSupport.scala
separate the FutureActorRef out into two parts
AskableActorRef
and
PromiseActorRef
going to implement
PromiseActorRef since I need it for some of the Akka.Remote stuff I'm doing today
my bad, I thought I had them using the same version
should we just standardize on the latest?
I haven't had time to look at Paket yet, heard good things though
@Horusiath so, is Paket easy to get going with? just dont want people to get overwhelmed with alien tech when they open up our code :)
for me control over dependencies versions on the solution level rather than each project level separately is strong nice to have
reminds me of Bundler from Ruby
was reading about the dependency management down the stack
not a fan of not allowing post-install scripts though, although that doesn't really affect Akka.NET at all
Paket doesn't change the Visual Studio NuGet package restore experience at all
it's a command line tool that fixes up the packages.config whenever it's run
to synchronize the versions with paket.lock?
@Aaronontheweb that's not the case. If you use Paket you don't have a packages.config anymore. Read this: http://fsprojects.github.io/Paket/paket-convert-from-nuget.html
I'll think on it then - have to weigh the benefits of what it does against the impact on the learning curve for people who want to contribute.
but I appreciate the goals of the project. I'll play around with it too
however, looking at the issue (#609) I lean towards what @smalldave said
probably not much of a learning curve once it's wired up in the RESTORE process
AFAIK Tail Chopping router is implemented, but it's not presented here: http://getakka.net/wiki/Routing
