> This century they have bought up LinkedIn, GitHub, npm, and a stake in Facebook. They have replaced Atom with a fauxpen source editor.

You left out the part where you explained why any of those acquisitions are a problem: LinkedIn is no worse than it was before, GitHub and npm are both popular services people choose to use without coercion, and whether or not you like it a lot of developers are switching to VSCode because it's a better tool which makes them more productive.

I don't what you believe to be true about their Azure integration but I know many people who use GitHub, npm, VSC, etc. and none of them use Azure so clearly there's some key step missing in that process.

Concentration of power is (or at least I thought it was) obviously bad. This is why there's laws protecting against that but either they're not enforced or they weren't updated to the internet age.

It is a concern but being popular is not the same as having high power: GitHub has lock-in to the extent that it's a great service but it's not exactly like they're changing Git to prevent you from using your own self-hosted service, Gitlab, BitBucket, etc. Similarly, VSCode is open-source with tons of competitors: where's the angle where they have much ability to dictate anything to users?

>They have replaced Atom with a fauxpen source editor.

I'm gonna counter this with the fact that VSCode was way better maintained and optimized than Atom.

The GitHub before Microsoft seemed to me as an company that would half-ass everything they could, and Atom was one of those things.

When VSCode came, at least to me, it absolutely destroyed Atom with versatility and stability.