Microsoft Dependency Has Risks

The trick with Microsoft is to very carefully separate the good parts from the bad ones.

Labeling all of Microsoft as banned is really constraining your technology options. This is a gigantic organization with a very diverse set of people in it.

There aren't many things like .NET, MSSQL and Visual Studio out there. The debugger experience in VS is the holy grail if you have super nasty real world technology situations. There's a reason every AAA game engine depends on it in some way.

Azure and Windows are where things start to get bad with Microsoft.

How do you separate the good from the bad? What do you do when Microsoft changes the good things into bad things?

My take is that Microsoft consistently makes bad things and makes "good" things into "bad" things; so, I don't have much expectation or faith that anything that I currently think is "good" will stay that way.

> How do you separate the good from the bad?

Developer tools and enterprise stuff good (mostly). Consumer products bad.

For whom? Microsoft?

I don't know which of their developer tools I would consider good. Or less worse than the competition