Why are Linux and MacOS discourged with very large libraries?

[Andreas_Philipp1]

@Michael_Harris

While I don’t know this for sure, it could well have been related to the old Mono requirements as a runtime for DotNet. This has mostly gone with the availability of DotNet 6 and that has been rolled out and it seems to have stablised the memory leaks and improved performance.

I too think this recommendation is outdated and that it had to do with the fact that for a long time Windows and ROCK were the only supported platforms based on native .NET. On Linux and Mac OS, Roon depended upon the Mono libraries which showed bad memory management behavior in comparison with .NET and in general were not as performant.

While several months ago Roon for Linux was released with native .NET 6.0 support and is now behaving much better than before, this is still not the case for Mac OS. There are lots of users who run very big libraries on Linux (best on a minimal Linux server installation), but until Roon can deliver the port to .NET 6.0 on Mac OS, I wouldn’t intend to run a big library on it.