Who likes stats? Here are stats for the (unversioned) namespaces in AzureNative:

Number of namespaces: 448
Number of classes: 14686
Largest namespaces (most classes):
    Pulumi.AzureNative.Network: 671
    Pulumi.AzureNative.DataFactory.Outputs: 530
    Pulumi.AzureNative.DataFactory.Inputs: 514
    Pulumi.AzureNative.Web: 389
    Pulumi.AzureNative.Network.Outputs: 303
    Pulumi.AzureNative.ApiManagement: 274
    Pulumi.AzureNative.Network.Inputs: 261
    Pulumi.AzureNative.Sql: 255
    Pulumi.AzureNative.DataMigration.Outputs: 179
    Pulumi.AzureNative.Insights: 179
    Pulumi.AzureNative.RecoveryServices.Outputs: 177
    Pulumi.AzureNative.Compute: 173
    Pulumi.AzureNative.DocumentDB: 170
    Pulumi.AzureNative.Compute.Outputs: 152
    Pulumi.AzureNative.ContainerRegistry: 147
    Pulumi.AzureNative.Logic: 140
    Pulumi.AzureNative.DataFactory: 135
    Pulumi.AzureNative.Media: 135
    Pulumi.AzureNative.Cdn: 128
    Pulumi.AzureNative.RecoveryServices.Inputs: 128
Most used class names:
    SystemDataResponse: 46
    SkuResponse: 44
    SkuArgs: 43
    PrivateEndpointConnectionArgs: 39
    GetPrivateEndpointConnection: 31
    GetPrivateEndpointConnectionArgs: 31
    GetPrivateEndpointConnectionResult: 31
    PrivateEndpointConnection: 31
    PrivateEndpointResponse: 26
    PrivateLinkServiceConnectionStateResponse: 23
    ResourceIdentityType: 23
    PrivateLinkServiceConnectionStateArgs: 22
    PrivateEndpointConnectionResponse: 21
    SkuName: 20
    IdentityArgs: 14
    IdentityResponse: 14
    PrivateEndpointServiceConnectionStatus: 13
    Account: 13
    AccountArgs: 13
    GetAccount: 13
Number of class collisions if the 'Inputs' namespace were removed: 40
  (example: 'Pulumi.AzureNative.CognitiveServices.PrivateEndpointConnectionArgs' and 'Pulumi.AzureNative.CognitiveServices.Inputs.PrivateEndpointConnectionArgs')

I started exploring this because a) I dislike having two namespaces for every resource I create (and remembering which classes are in where) and b) when creating multiple resources in a single stack, I often have to more fully qualify namespaces to deal with ambiguous class names.