Stride Game Engine VS Orleans

In general it took me less time to rewrite the code-base then implementing some of the workarounds for missing features in Unity (e.g. HTTP2) in the first place.

[0] https://github.com/stride3d/stride/issues/2069

I don't know where you have all these GC problems. There must be a problem with your design. I run real time automation stuff in C#, GC doesn't caused any problem yet. Stride3D docs says, that's if you put a lot of big objects in the heap without reusing them, you will hit big GC pause: https://github.com/stride3d/stride/wiki/On-Garbage-Collection But most of the time it's trivial to reuses those.

This could be set as a prominent link somewhere, it is the official stride forums: https://github.com/stride3d/stride/discussions

If you like to develop in C#, the free and open-source game engine Stride is a good alternative. But it really depends on your needs and skill level: https://github.com/stride3d/stride

> ...you are requested to delete The Machinery source code and binaries.

This is pretty weird.

Then again, in regards to the engine itself dying, I feel like this is inevitable for many of the projects out there. For example, there was the Xenko engine which was later renamed to Stride: https://www.stride3d.net/

It's actually a nice project, has lots of great features and feels like it should be a more open alternative to Unity, whilst being similarly easy to use. However, compare the attention it is getting in comparison to something like Godot:

  - https://github.com/stride3d/stride

I leave this little thing: https://stride3d.net

We should chat more about Reminders v2 - I want to learn more about what you'd like it to provide. Can you comment on the issue (https://github.com/dotnet/orleans/issues/7573)? If you'd like to see some of what is in the works, please message me on Discord and we can chat more about it (https://aka.ms/orleans/discord)

for ADO scripts config, I ran the main, clustering, and persistence scripts but got runtime error lacking some migration sql object (don't remember the exact error message). But after some debug, I had to run this extra migration script which was not mentioned in that ADO config page.

I think Orleans is going to introduce something similar that Temporal has on .NET 8 https://github.com/dotnet/orleans/issues/7487

Something tells me that the developers should have cleared batchOperation a bit later. Judging by the fix, the Orleans developers agree with me.

Dapr is created for multi language purpose. If you have only .NET Stack there is mature and more faster Microsoft Orleans. Debugging is easy with local silo - just debugging the same process.

There are some more perf improvements coming to Orleans serializer, like this 1.6x improvement to message serialization: https://github.com/dotnet/orleans/pull/8185