News for hackers. Stuff that matters.
Re:GitHub is no longer independent at Microsoft after CEO re... by yencabulator on Monday August 11, 2025 @04:55PM (#44869356)
> I honestly don't remember when they tried to snare someone to use proprietary extensions to something open.

Try using VSCodium legally with the same functionality as VSCode; remote development, Python language server, C++ debugging, and so on.

People who think Microsoft is doing open source work for the good of their hearts are still in for a lesson in EEE.

https://github.com/VSCodium/vscodium/blob/master/docs/extens...

https://github.com/VSCodium/vscodium/blob/master/docs/extens...

https://github.com/microsoft/vscode-cpptools/wiki/Microsoft-...

https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...

Re:GitHub is no longer independent at Microsoft after CEO re... by ivanmontillam on Monday August 11, 2025 @05:19PM (#44869588)
As GP said:

> Long story short: MS isn't a saint. They are a business. And they have behaved relatively nice for so long that some young adults don't know any other side of MS now.

They are a business. You seem to misunderstand that businesses cannot behave like charities.

Being a business implies being for-profit.

Nobody said open source had to be free as in free beer, it just had to be free as in freedom.

It's their prerogative to make the plugins marketplace to alternative editors or not. Servers cost money. It's a business.

Does Matt Mullenweg has to let WPEngine sap server resources? Arguably not; and this opinion comes from a guy (me) that strongly dislikes WordPress (and by extension: Matt and Automattic).

Re:GitHub is no longer independent at Microsoft after CEO re... by yencabulator on Monday August 11, 2025 @05:35PM (#44869740)
I am responding to this:

> I honestly don't remember when they tried to snare someone to use proprietary extensions to something open.

Re:GitHub is no longer independent at Microsoft after CEO re... by yesbabyyes on Monday August 11, 2025 @05:42PM (#44869806)
Matt Mullenweg did nothing wrong
Re:GitHub is no longer independent at Microsoft after CEO re... by sebastialonso on Monday August 11, 2025 @09:01PM (#44871213)
Man, more than two decades of open source and people still don't understand what free as I'm freedom means. It's depressing.
Re:GitHub is no longer independent at Microsoft after CEO re... by thiht on Monday August 11, 2025 @06:13PM (#44870059)
These are extensions. No one is preventing OSS communities from developing their own remote dev, Python, and C++ extensions. The VSCode extension API allows it. There are actually some efforts being made to do it.
Re:GitHub is no longer independent at Microsoft after CEO re... by sdenton4 on Monday August 11, 2025 @06:18PM (#44870109)
Ah, but coming hot on their heels are the embracions and extingushions!
Re:GitHub is no longer independent at Microsoft after CEO re... by yencabulator on Monday August 11, 2025 @06:16PM (#44870086)
You're moving the goalposts! I am responding to

> I honestly don't remember when they tried to snare someone to use proprietary extensions to something open.

Re:GitHub is no longer independent at Microsoft after CEO re... by fc417fc802 on Tuesday August 12, 2025 @02:07AM (#44872947)
But ... they literally did that here? I don't think it's malicious in this case. In fact I think they're giving away genuinely useful tools here with no obvious downsides to their use.

But I do think it qualifies.

Bit like the example of Martin Luther King being a criminal.

Re:GitHub is no longer independent at Microsoft after CEO re... by nothrabannosir on Tuesday August 12, 2025 @12:52AM (#44872515)
You’re describing the E in EEE
Re:GitHub is no longer independent at Microsoft after CEO re... by croes on Tuesday August 12, 2025 @07:33AM (#44874946)
I think it's not about the extensions but the market place.

You can't use the MS extensions with VS Codium, you are forced to use VS Code.

Re:GitHub is no longer independent at Microsoft after CEO re... by gmueckl on Tuesday August 12, 2025 @02:09AM (#44872963)
Oh, I honestly didn't remember the VS Code extension shenanigans. Thanks for bringing that up.