this post was submitted on 20 Oct 2023
60 points (96.9% liked)

Programming

17490 readers
79 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

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
snowe
Ategon
[email protected]
60
Visual Studio Code is designed to fracture (ghuntley.com)
submitted 1 year ago by [email protected] to c/programming
22 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] 5 points 1 year ago

But JetBrains has a good track record of not enshittifying and, because you actually pay for their product

I disagree.

Jetbrains is going essentially the same way with kotlin. Even though it's open source on paper, Jetbrain is gatekeeping it to a degree where they are actively blocking changes that would make it easier for LSP developers to integrate (thus potentially creating competition to their intellij products ).