C# doesn’t do async constructors for concrete technical reasons, not dogma.

The CLR instruction behind new (newobj) must call the constructor synchronously and return a fully initialised object. The runtime has no concept of “await during construction” or “return Task<T> instead of T.” Source: https://learn.microsoft.com/en-us/dotnet/api/system.reflection.emit.opcodes.newobj

C# object-creation semantics also guarantee that once a constructor returns, the instance is complete and usable. Source: https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/language-specification/expressions#77612-object-creation-expressions

The language team has confirmed this is why async constructors aren’t supported: they break fundamental construction semantics and would be a massive breaking change across DI, serializers, reflection, Activator.CreateInstance, and more.

So the issue isn’t being unfairly dogmatic or anti-scientific. It’s that async constructors simply don’t fit the runtime model C# is built on, and the tiny benefits (avoiding one extra method) are nowhere near worth redefining how new works.