Containers are the future
the actor model they're exposing is a programming framework for being able to leverage these capabilities on the Service Fabric runtime
because the low-level APIs for using it are extremely complicated and unfriendly
I have friends on the SQL Azure team who used themd
so this stuff aligns really well with Akka.NET too
I don't know the rest of the details
But I guess this is for the best
MS is in a "throw it on the wall and see what sticks" phase
the kindness they've done us is OSS the CLR and make it so the .NET ecosystem is no longer solely dependent on them
MSFT has always had that problem
they go out and make it so you can run Hadoop on Azure
then simultaneously roll out their own propreitary version of MapReduce
and then also kill off Dryad (another proprietary M/R implementation they'd been doing for years out of MSR)
the criticism I would level at Microsoft is to knock if off with the "not invented here" shit
because frankly they haven't been that good at it on a lot of fronts
i.e. Metro UI
focus on supporting the ecosystem - not trampling over it with half-baked shit
the talks I really wanted to see at .NET Fringe were the Nancy talks
I was pretty blown away by both Nancy and ScriptCS
@nvivo big difference is that the message queue is a required implementation of the mailbox
so you can say "I want a PriorityMailbox"
(that's what WithMailbox is for)
but if your actor uses a stash then is also decorates itself with a
IRequiresDequeSemantics interface
which means that its
PriorityMailbox implementation must support a double ended queue for stashing
so both values get respected
one is just a lower-level abstraction than the other
the message queue requirement gets fulfilled by the mailbox when it's created
Ok