"EEE" isn't a magic incantation, it's the name of an actual policy with actual tangible steps that their executives were implementing back when the CEO thought open source was the greatest threat to their business model.
Microsoft contributing to a project doesn't automatically make it EEE. For one thing, EEE was about adopting open standards in proprietary software. Microsoft during EEE didn't publish GPL code like this is.
Well, most of their extensions to VSCode are proprietary. When their dominance in software development becomes irreversible, it's obvious that they will close things down and create new sources of income. The incentives are clear.
The fix described in this post have been submitted as a patch to the official Git project. The fix is improving a legitimate inefficiency in Git, and does nothing towards "embracing", "extending", or "extinguishing" anything.
Can you imagine their fork extending git with a feature which is incompatible to mainline git and then forcing user's to switch to their fork via github? I can, and it will give them the power to extinguish mainline git and force everything they want on their users (telemetry, licence agreements, online registration...). That might be the reason they're embracing git right now. The fork being open source doesn't help at all.
I'm not saying this shouldn't be merged, but I think people should be aware and see the early signs.
They will extend git so that it works extremely well with their proprietary products, and just average with other tools and operating systems. That's always the goal for MS.
PoignardAzur|1 year ago
"EEE" isn't a magic incantation, it's the name of an actual policy with actual tangible steps that their executives were implementing back when the CEO thought open source was the greatest threat to their business model.
Microsoft contributing to a project doesn't automatically make it EEE. For one thing, EEE was about adopting open standards in proprietary software. Microsoft during EEE didn't publish GPL code like this is.
haolez|1 year ago
atombender|1 year ago
The fix described in this post have been submitted as a patch to the official Git project. The fix is improving a legitimate inefficiency in Git, and does nothing towards "embracing", "extending", or "extinguishing" anything.
clktmr|1 year ago
I'm not saying this shouldn't be merged, but I think people should be aware and see the early signs.
dijit|1 year ago
it will look good, until the extensions get more and more proprietary- but absurdly useful.
Alifatisk|1 year ago
throwuxiytayq|1 year ago
coliveira|1 year ago
szundi|1 year ago
I find these insightful reminders. Use the vanilla free versions if the difference is negligeble.
maccard|1 year ago