I feel like Microsoft's naming division has a mandate to cause as much name collision as possible, so that "out of date" requirements at very big very slow ente

I feel like Microsoft's naming division has a mandate to cause as much name collision as possible, so that "out of date" requirements at very big very slow enterprises suddenly and magically target the latest hotness. It is my main gripe with the .NET ecosystem. Don't get me started on Azure.. But once you get over the hump and understand the meaning of the subtle differences, it's possible to make sense of it.