Revisit default log handler behaviour

[QuintinWillison]

Our .NET SDK, at the time of writing this, defaults to outputting to Debug.WriteLine(). This has the result that the information is available in the output window, but not in the command line (standard output, stdout).

Going strictly by RSC2 and RSC3, this could be viewed as a bug in the .NET SDK. Conversely, if we apply our more recent imperative to be more language/platform idiomatic, then this choice for the .NET SDK could be viewed as preferable.

Perhaps this has something to do with the different runtime contexts for .NET. For a GUI or game application, then perhaps the output window is the most logical place for debug output. However, for a command line application, perhaps stdout or stderr is preferable. 🤔

┆Issue is synchronized with this Jira Task by Unito

[sync-by-unito]

➤ Automation for Jira commented:

The link to the corresponding Jira issue is https://ably.atlassian.net/browse/SDK-2768