• sizeoftheuniverse@programming.dev
      11·
      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.

  • joneskind@lemmy.world
    91·
    1 year ago
    • Install VSCode
    • Install all extensions
    • Copy extensions folder
    • Install Codium
    • Move extensions to Codium extensions folder
    • Remove VSCode
    • voxel@sopuli.xyz
      2·
      1 year ago

      or just use the vscode marketplace in codium…

      you can also just use openvsix, which actually contains everything you’ll ever need

      • Marxine@lemmy.ml
        1·
        1 year ago

        As long as the same extensions exist in its repositories, yes. VSCodium has its own extension marketplace though, many of the most used can be easily found there.

    • ScandalFan85@feddit.deEnglish
      1·
      1 year ago

      You can also download the *.vsix file of the desired extension from either Github or Microsoft’s extension marketplace and install it manually by clicking on “Install from VSIX” in the Extensions menu.

      This obviously doesn’t solve the update problem and it is also questionable if this is in terms with the “Microsoft Terms of Use” of the extension.

  • DonnerWolfBach@feddit.de
    2·
    1 year ago

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

        • sugar_in_your_tea@sh.itjust.works
          1·
          1 year ago

          Vim chocked for me when I tried to launch it with git commit -v with a massive changeset (~100 files, lots of small changes per file), and neovim was cool with it.

          So neovim is just a little bit smoother.

      • heartlessevil@lemmy.one
        1·
        1 year ago

        Why not both? I’ve used Emacs with evil-mode for several years. I did use Vim before that for longer though.

        • psilocybin@discuss.tchncs.de
          1·
          1 year ago

          If you count that as both then I agree. I also use emacs with modal keybinds (not vim-style though)

          I just wanted to bring back the flame war a little sijce you were nostalgic about it

  • Rho@programming.dev
    1·
    1 year ago

    in linux I use codium and add a symlink from code to codium, that way software that only recognizes code will work with codium (don’t know why godot does it) and it works great, on windows I just couldn’t make it work so I use code because unity only works with code and I have to use Unity for work also, I enabled the vscode store in codium because there are some extensions I need that aren’t on the codium store

    • TechCodex@programming.devOP
      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
    02·
    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.

    • watermelonsushi@lemmy.fmhy.ml
      3·
      1 year ago

      I’m all for using vim or Emacs or whatever, and I agree that not having a dependency on a specific editing software is a great thing.

      But since when did using VSCode enforce the decision on other members of the team? VSC is just going to integrate it’s features with whatever build system you are using. It doesn’t enforce any particular build tool in any project. You can use NPM, yarn. PNPM, whatever the fuck else lol… Nobody needs to maintain multiple build systems to support VSC because it is also just a text editor, albeit a bloated one. Yes, if you install all the fancy extensions to integrate VSCode with your project, it will be a heavy app, and that’s a problem. But if you want your barebones editor, just don’t install any extensions? I’ve been in projects where I’ll be using VSC while someone else will be using Vim and that one dude will be using webstorm or something. It works. There is no MicrosoftTM build tool lockdown going on.

      I know vim is still far less resource intensive than code but outside of very specific use cases, I’ve never seen any modern computer struggle with running code, especially without the extensions… It’s equivalent to opening an extra chrome window, I’m sure most computers can handle that lol.

      End of the day the best tool is whatever lets you personally write code faster, and for some of us that happens to be VS Code