Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
Don't put all your eggs in one basket, don't put all your chickens in one barn and don't place all your barns on one farm.
I write C/AL for a living (a Pascal-like language) and F# in my basement (okay, so I don't have a basement).
Here is a list of Channel 9 staff members.
© 2013 Microsoft. Except where designated as licensed by
Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 License,
Microsoft reserves all rights associated with the materials on this site.
Announcing Channel 9 Notifications
Apr 11, 2013 at 12:22 PMBeen waiting for this!
Philips Hue Lighting Controller
Apr 08, 2013 at 9:50 AMPing 172: MVP Program, Developers get paid, TMall in China, Xbox hacked
Mar 25, 2013 at 11:26 PMHow 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.
Channel 9 turns 9!
Mar 25, 2013 at 6:52 AMCoincidentally, I now have 9 followers and am following 199 artists on Spotify! And my current profile was created in 2009.
Immo Landwerth and Andrew Arnott: Inside Immutable Collections
Mar 22, 2013 at 12:34 PMWesner Moise - previously a top blogger, now resurrected from deep sleep. I'll follow...
Channel 9 turns 9!
Mar 15, 2013 at 5:11 PMHappy birthday. This place rocks!
Tip 3: Wrap events up in Task-returning APIs and await them
Mar 14, 2013 at 5:20 PMThis pattern looks cool. I'm going to have a close look at this when doing the next C# project! Thanks for the tip!
Tomas Petricek: How F# Learned to Stop Worrying and Love the Data
Mar 05, 2013 at 11:06 AMIndeed, 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.
Programming the Cloud with Actors: Inside ActorFx
Feb 27, 2013 at 9:06 AM@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.
Programming the Cloud with Actors: Inside ActorFx
Feb 21, 2013 at 2:11 PMAnother 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.
See more comments…