8 karma · joined February 10, 2023
any
use case (except perhaps embedded) with .NET.
How so? Do you mean it doesn't support ephemeral ftrace-based tracing or something? That seems unlikely to be true given core CLR features like reflection as well as Microsoft's extensive history of embedding .NET into services and devices.
There is no gun violence in the US. There is violent crime. There is murder. They are different things.
Given recent trends in the development of AI, this is not something I would be holding my breath for.
Does anybody know what they are?
Does anybody know if builders are required to follow them?
Restricting your usage tracking to your users is fine until you start shouting to them directly on their phones.
Async frameworks don't eliminate the possibility of long running processes, that continue to process long after responding a request - this is still possible with specific libraries/frameworks, they'll only take away the synchronous interface and provide as asychonous one instead.
It is also important to note that error handling will be different between these 2 paradigms and it's important, whatever the most suitable one is, to acknowledge this since it forces us (developers) to handle the potential errors differently depending on the approach we choose.
Bottom line: enabling this doesn't hurt. It might help, and it doesn't cost anything to check
[1]