• joneskind@lemmy.world
    link
    fedilink
    arrow-up
    7
    arrow-down
    1
    ·
    1 year ago
    • Install VSCode
    • Install all extensions
    • Copy extensions folder
    • Install Codium
    • Move extensions to Codium extensions folder
    • Remove VSCode
    • sizeoftheuniverse@programming.dev
      link
      fedilink
      arrow-up
      0
      arrow-down
      1
      ·
      1 year ago

      That was exactly my experience with it.

      I was using VIM in the old days, so I already had some memories on now to do basic editing.

      And then I’ve spent a week trying to make NeoVIM a well adjusted IDE for C, Java, JavaScript and go. I’ve quit after a week, as the results were not satisfactory.

  • DonnerWolfBach@feddit.de
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I use vscodium for most day to day stuff and vscode for trying out/“sandboxing” specific extensions like github copilot.

    • TechCodex@programming.devOP
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      VSCodium has limited plugins, but most known ones were available… Weird logo, some kind of a seaplant?? But I soon dig it…

      VSCode has all the plugins, but with Microsoft’s Telemetry as expected… Cool logo…

      Truth: I’m using VSCodium, the absence of Telemetry tends to improve it’s overall performance… I’m beginning to like the logo… Plugins support has improved, all the plugins I used in VSCode, are now available… All of it…

  • nothacking@discuss.tchncs.de
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    1 year ago

    Vim, nano, micro, emacs… ffs. Your text editor should not be a shell, a file manager, a compiler, a build system or a dependency manager. Do one thing and do it well, a editor that tries to be everything ultimately becomes an inflexible mess. An integrated system often becomes an interdependent system, where you are stuck with a single build system, version control, compiler, or file manager. When these are separate tools, they are interchangeable, one person can use vim, the other nano, a third gedit. One project can use make, a second ninja or meson.

    If a project uses VScode, it basically forces everyone else to use it or forces you to maintain two separate build systems. Another option is to only use external tools, but then VScode just becomes an extremely bloated text editor. On my computer, both vim and emacs, start before I can lift my finger from the enter key. The same can’t be said about VScode.