News for hackers. Stuff that matters.
Re:Orleans – Distributed Actor Model by CmonDev on Monday January 26, 2015 @09:11AM (#8947046)
https://groups.google.com/forum/#!topic/akka-user/C0WGdTs2gy...

"One other thing is that the way these entities are presented to the user is via static nominal interfaces, which precludes the kind of freedom an Actor shall have according to the model (technically it also fails on the count that actors can create other actors, so it only implements message passing and misses actorOf() and become()). Therefore I would not call it an implementation of the Actor Model."

http://www.infoq.com/news/2014/07/approaches-actor-model-net

"Sergey answered by claiming that Become is just one way of reading the definition and therefore not a requirement of the actor model."

PS: having been burnt with WPF and XNA, I would rather go with Akka.NET:

1) not likely to die;

2) cross-VM (CLR, JVM);

3) based on the "standard" interpretation of the Actor Model.

Re:Orleans – Distributed Actor Model by sudioStudio64 on Monday January 26, 2015 @09:45AM (#8947199)
I get what you are saying... I'm just wondering why you feel burned by WPF. They've recently announced that it will be under active development for many years to come. Granted, they've announced new application models, but they haven't abandoned WPF.

Akka.net has been developed as open source for longer and benefits greatly from that, but Orleans is open source and is being used by internal teams at MS...im not sure how that really compares to the uses of akka, but its not really "abandonware".

Re:Orleans – Distributed Actor Model by CmonDev on Monday January 26, 2015 @12:11PM (#8948116)
Do you notice any major time gaps between WPF team blog posts here?

http://blogs.msdn.com/b/wpf

Like 4-year gap at the top? I have switched to ASP.NET Web API within that gap. That kind of silence killed any trust, that cannot be fixed by appointing some unknown manager and adding a couple of minor features. What is active development? Azure is in active development. Asp.NET is in active development. WPF is barely alive.

Re:Orleans – Distributed Actor Model by sudioStudio64 on Monday January 26, 2015 @12:20PM (#8948202)
People are still building software that makes real money using MFC and ATL. Maybe the feature set just matured? I'm not saying it doesn't need improvement...like Windows forms...people still make money with it.

It's not like knowing XAML became useless...the new app model uses it as well.

Re:Orleans – Distributed Actor Model by CmonDev on Monday January 26, 2015 @12:52PM (#8948386)
People can make any money they want with any technology - even COBOL could work for business. As an employee I want very good money _and_ a broad set of opportunities (not some unicorn maintenance gigs).

It's not like knowing XAML became useless... More like the whole world moved on to HTML (no matter how crappy it is and it is very). Where are the WPF Disciples? Where are the XAML Disciples? Where are dozens of XAML GitHub repos? Just the tumbleweed rolling across the desert...

Re:Orleans – Distributed Actor Model by pjmlp on Monday January 26, 2015 @11:39AM (#8947899)
Some .NET devs tend to separate WPF from the XAML stack.

Personally I never though of myself as having WPF skills, rather XAML stack skills.

All the concepts, XAML, bindings, MVVM, ... are applicable to WPF, Silverlight and Metro, even if the APIs are a little different.

Re:Orleans – Distributed Actor Model by sudioStudio64 on Monday January 26, 2015 @12:15PM (#8948157)
That's kind of what I have always thought would be a reasonable way to approach it...I'm not doing UI development,so I can't speak to the API diffs. Are there major gaps in functionality?
Re:Orleans – Distributed Actor Model by pjmlp on Monday January 26, 2015 @02:49PM (#8949140)
So far I have stayed on the WPF side, but from I have dabbled, some ways how bindings work and support for Blend interactions.