Comments

Been waiting for this!

How about giving incentives like 100% profits and free tools for the first one or two apps instead?

That said, Microsoft used to create reference applications like Family.Show to show how to build good applications for their platform - or rather they wold pay another company to do it. Is that still the case? (And how about upgrading those apps for familiarity for devs?)

Maybe if you want to attract dev's you need to set more high quality examples and release the source on GitHub and Codeplex. Also comparative code for other platforms to show off benefits of async etc.

Coincidentally, I now have 9 followers and am following 199 artists on Spotify! And my current profile was created in 2009.

Wesner Moise - previously a top blogger, now resurrected from deep sleep. I'll follow...

Happy birthday. This place rocks!

This pattern looks cool. I'm going to have a close look at this when doing the next C# project! Thanks for the tip!

Indeed, this is a very cool series of demonstrations.

The F# type provider feature is really blossoming under the open source movement.

Excellent presentation!

In my last project I could have used the Type Script / FunScript type provider.

@joe hoag: With respect to P2P, I'm not sure, my thought was just that actors in different run-times could perhaps talk to eachother since access to state happens through methods (or events), so the state itself can be locally shielded. Therefore calling an "external actor" would be analogous to calling a (Web) [Service] method. How such a P2P protocol for talking between actors would look like I don't know; it's just a vague idea at this point. But in the WS realm there are concepts like Web Service discovery. So why not a similar concept for distributed actors (whether a peer happens to be a node in a cloud datacenter, a cellphone or a workstation)? But I'm new to actors.

Another question is if you can dynamically discover actors and their methods - as if they were Web Services. Perhaps this could be coupled with F# 3 type providers via an actor type provider to "dot into" actors, their methods (or events) and the returning state.

In this open world, perhaps you can even allow your actors to interact with "foreign actors" - other applications in a truly internetworked way - and perhaps associate billing semantics to method calls or data and CPU usage.

Mesh into that P2P actors and this will be quite the interesting creature.

It could also turn into a brittle beast perhaps - when API's change in an open world and things start to break - transitively.