In this blog post, we explore the ecosystem of open-source forks, revisit the story so far with how Microsoft has been transforming from products to services, go deep into why the Visual Studio Code ecosystem is designed to fracture, and the legal implications of this design then discuss future problems faced by the software development ecosystem if our industry continues as-is on the current path…
I did not understand anything
Vscode is beginning it’s enshittification cycle. They got everyone using it, now they start locking it down. Much of the fear is what Microsoft could do, not so much what they have done so far
The C# extension going proprietary is the smoke to the coming fire though, and highlights what could happen to other languages. The new extension cannot be installed on open source redistributions like vscodium. What happens now if the typescript extension gets a similar update? Or Python? Etc.
They’ve made it so technically anyone can spin off their own extensions marketplace, and attempt to make their own C#/typescript/Python extensions, but can they truly compete with Microsoft? That is the fracture the author is talking about. They’ve effectively made a walled garden out of an open source platform, they’ve just been playing nice to hook devs and companies in before the slow enshittification
That’s not enshitification, that’s Embrace-Extend-Extinguish and it predates Cory Doctorow’s ego.
“Its MIT open source and anyone can use it!”
The MIT codebase is just bait
We have VSCodium and you can use a plethora of extensions with that one no problem.
I think when it becomes a problem it won’t be hard for the community to build their own extensions that can be used anywhere. It doesn’t hurt right now so that work hasn’t been done yet.
Will it ever hurt though? Its designed to make things like GitPod feel uncomfortable while making VS Code feel good.