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
    link
    fedilink
    arrow-up
    2
    arrow-down
    4
    ·
    edit-2
    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
        link
        fedilink
        arrow-up
        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.