4 ms·
I wonder if this will also impact VSCodium. I use it specifically to avoid a lot of the crap that Microsoft is trying to do while still being able to use the ed
by nerdjon 10mo ago
I wonder if this will also impact VSCodium. I use it specifically to avoid a lot of the crap that Microsoft is trying to do while still being able to use the editor and plugins.
They have not released 1.107 yet, doing a quick scan I am not seeing anything on the VSCodium github.
- catapart 10mo agoSame boat. I hope they don't downstream nonsense like this.
- __jonas 10mo agoI didn’t think it was even possible to install proprietary microsoft extensions in VSCodium, how is that related to the version of the editor and how would it affect VSCodium?
- NGRhodes 10mo agoIt is not possible to install proprietary Microsoft extensions using the official VSCodium builds without additional, non-default configuration.
- __jonas 10mo agoRight. Then the removal of this IntelliCode extension from MS should have no effect on VSCodium users. I thought originally it may have been an OSS extension, but it actually seems to have been a proprietary project licensed under the Microsoft Software License, similar to Copilot and such.
- ghuntley 10mo agoeven then using vscodium does not free you from the grasps. vscode by design is designed to fracture - see https://ghuntley.com/fracture https://ghuntley.com/fracture
- phba 10mo agoThanks for the link. This is a great analysis of Microsoft's open source strategy.
- danvayn 10mo agoIntellicode being (officially) deprecated will impact VSCodium, yes. I too am more concerned about copilot being further “needed” or required in my VSCode fork. It’s already the biggest pain in the butt I’ve ever had to deal with in the context of VSCodium. I am not excited for the future.