I used to think GitHub Codespaces would help popularise Gitpod but now realize it is the other way around. Gitpod is currently permitted to exist in the Visual Studio Code ecosystem to popularise GitHub Codespaces, and Microsoft can step in at any moment to create legal crises that strategically divide the market from a business perspective because, like Apple and their AppStore: it is their ecosystem that they control and they are in absolute control.

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…

  • jeremyparker@programming.dev
    26·
    1 year ago

    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

      • robinm@programming.dev
        2·
        1 year ago

        I need to re-try it. I really like like lsp/dsp are first class cityzen, including the keybindings, and that there is better text objects than in vanilla neovim. Last time I tried it there was a few things that where not that easy to set-up (I forget what), but I should definitively take the time to learn it.

        I just wish that neovim/kakoune/helix had a marketplace just like vscode. It make the discovery and installation so much easier when everyone use the same tools.