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…

  • armchair_progamer@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    It’s funny because, I’m probably the minority, but I strongly prefer JetBrains IDEs.

    Which ironically are much more “walled gardens”: closed-source and subscription-based, with only a limited subset of parts and plugins open-source. But JetBrains has a good track record of not enshittifying and, because you actually pay for their product, they can make a profitable business off not doing so.