Programming

17378 readers

148 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 !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

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

submitted 1 year ago by ck_@discuss.tchncs.de to c/programming@programming.dev

17 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

[–] jeremyparker@programming.dev -2 points 1 year ago* (last edited 1 year ago) (4 children)

That's so weird, I thought everyone had already heard about neovim. Why are people still using vs code?

Now that vim has consumed the corpse of the emacs vs vim debate, it has only grown larger, and more ravenous

[–] tatterdemalion@programming.dev 9 points 1 year ago (3 children)

That's so weird, I thought everyone had already heard about Helix. Why are people still using neovim?

load more comments (2 replies)