Oh btw, there was no conflict of interest from your side? _Your_ company did not want to follow the maturity scale, so you made an effort to shoot the proposal

Oh btw, there was no conflict of interest from your side? _Your_ company did not want to follow the maturity scale, so you made an effort to shoot the proposal down... How does that make you better than Microsoft? As for customers... there will always be customers for pre-packaged solutions, quality and support. Obviously .net cannot include a framework for $X for every possible X. But that does not mean that non-customers of yours are _not_ doing (approximations, to the degree they need) of X internally. In your posts, you were complaining about the lack of innovation, yet Akka.NET (I assume that's what you're referring to) does not seem to innovate anything, it's a carbon-copy of Akka for Java and the "raw" actor model. Project Orleans from MSR on the other hand _does_ innovate. I have a PhD related to distributed systems and I investigated the actor model a lot. Orleans addresses the deficiencies/problems with [1] it that I myself noticed. [1] Quote from the introduction of https://www.microsoft.com/en-us/research/publication/orleans-distributed-virtual-actors-for-programmability-and-scalability/ https://www.microsoft.com/en-us/research/publication/orleans...: "Actor platforms such as Erlang [3] and Akka [2] are a step forward in simplifying distributed system programming. However, they still burden developers with many distributed system complexities because of the relatively low level of provided abstractions and system services. The key challenges are the need to manage the lifecycle of actors in the application code and deal with inherent distributed races, the responsibility to handle failures and recovery of actors, the placement of actors, and thus distributed resource management. To build a correct solution to such problems in the application, the developer must be a distributed systems expert."