Programming

17405 readers

116 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago

MODERATORS

[email protected]

Visual Studio Code is designed to fracture (ghuntley.com)

submitted 1 year ago by [email protected] to c/[email protected]

18 comments fedilink hide all child comments

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...

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 18 points 1 year ago* (last edited 11 months ago) (1 children)

"Its MIT open source and anyone can use it!"

But Microsoft only publishes a not-MIT licensed one
And if you DONT use that one, the extension store created by microsoft wont work
And even if you make your own extension store (which people did for VS Codium) you legally wont be allowed to use any of the de-facto quality of life extensions (Python, SSH, Docker, C#, C++, Live Share, etc)
And those extensions default to needing fully-closed-source tools develped by microsoft
AND, unlike Chromium, anything that tries to fork and build on top of VS Code, (e.g. gitpod; a web-based dev environment) will die because none of the de-facto/core/quality-of-life extensions people are used to will be available. They'll have to use the Microsoft alternative (e.g. Github workspaces)

The MIT codebase is just bait

[–] [email protected] 2 points 1 year ago (1 children)

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.

[–] [email protected] 3 points 1 year ago

Will it ever hurt though? Its designed to make GitPod just feel uncomfortable while making VS Code feels good.