12 ms·

I think the parent comment is talking about System.Threading.Tasks. I might be wrong though.

• bmitc 3y ago
  Oh, I see. I was hoping for something new. I keep on hoping some sort of BEAM-like (from Erlang) process gets added to .NET.
  • menacingly 3y ago
    I have considered the that, but I ultimately decided they work because they are a fabric of what that ecosystem _is_, not what it has. It's the same reason two sites that are more or less the same will have entirely different communities. There isn't any reason you couldn't implement the one on the other, but it's not in the core substance.
  • valcron1000 3y ago
    It was tried and the dotnet team decided to drop it: https://github.com/dotnet/runtimelab/issues/2398 https://github.com/dotnet/runtimelab/issues/2398
    • custard42 3y ago
      investigations continue: https://github.com/dotnet/runtime/issues/94620 https://github.com/dotnet/runtime/issues/94620
  • zengid 3y ago
    You might be interested in Orleans: https://learn.microsoft.com/en-us/dotnet/orleans/overview https://learn.microsoft.com/en-us/dotnet/orleans/overview
    • bmitc 3y ago
      Orleans is definitely interesting, but I have never looked into it much because it's my understanding that it is a cloud-only solution, in that it requires some Orleans or Azure service. Is that correct?
      • jen20 3y ago
        No, you can run in standard processes - there's even documentation [1] about hosting it in Kubernetes. [1]: https://learn.microsoft.com/en-us/dotnet/orleans/deployment/kubernetes https://learn.microsoft.com/en-us/dotnet/orleans/deployment/...
      • Rapzid 3y ago
        Further to the other reply you can run it alongside asp.net; one process can be an Orleans node and and an asp.net server.