3 ms·
After some level of tenure, many executives lose the feeling of being told no. If they have a strategic initiative they want to push (e.g. increase lock-in betw
by dannyw 5y ago
After some level of tenure, many executives lose the feeling of being told no. If they have a strategic initiative they want to push (e.g. increase lock-in between .NET and Visual Studio), they've lived and worked in a culture where they can make decisions without impunity or anyone saying to say no; so why would they care about a bunch of random github comments?
To them, I doubt the community even feels like humans. They're numbers in a spreadsheet: userbases to be monetised; cattle to be bred and slaughtered for beef.
From the Verge article:
> Sources describe the move as a business-led decision, and it’s clear the company thought it would fly under the radar and not generate a backlash.
TL;DR is that some exec high up thought this would increase their KPIs, and have enough fear in the org chart (from 29 years of tenure and being a Corporate Vice President) that no one dares to question.
Let this action be clear: no matter how much a PR team spins, Microsoft's "open source" initiatives will never, ever, come close to true open source projects like Linux or SQLite.
- passivate 5y agoLong term, its best to seek alternative means of funding, and reduce dependence on them. I don't think a commercial for-profit company should be on the hook to subsidize free software. The bottom line here is that the entity paying developers for their time has a very important say in what code they're going to work on.