• @GreenKnight23
    link
    91 month ago

    all I’m learning from these stories is to stay far far away from vscode.

    • Dragon Rider (drag)
      link
      fedilink
      English
      81 month ago

      You can avoid this problem by not doing version control in your code editor. Different programs for different purposes. VS Code is fine for editing code and should not be used to manage an entire project.

    • tiredofsametab
      link
      fedilink
      61 month ago

      I begrudgingly switched to vscode a few years ago. I’ve never had any issues like this with it. My only issues have been with a plugin that I installed optionally (and that was later fixed by the plugin author).

    • @CaptPretentious
      link
      4
      edit-2
      30 days ago

      VSCode is absolutely fine.

      Most of these comments can be reduced to either

      1. I use CLI by the way…

      2. Hating on VSCode because it’s Microsoft product and for no other reason.

      A Gitlab/GitHub account is free. VSCode absolutely lets you type git commands if you prefer that, The GUI only provides access to the most common actions you will do. And I could be wrong on this, but I feel like the discard button does prompt the user that the files will be permanently deleted and you have to click okay. But maybe that only applies to tracked files, not sure off the top of my head.

    • Cethin
      link
      fedilink
      English
      21 month ago

      (VS)Code(ium) is great. (VSCode is MS fork of the OSS Codium.) It’s a popular editor with a lot of plugin for just about every language. It has an integrated console. It can do basic Version control (and you can use the console for anything more). It’s my favorite editor/IDE (not technically and IDE, at least out of the box). Just don’t do things you don’t understand. It’s that simple. The OP fucked around, and they found out what it does the hard way. It’s really easy to use if you have a basic understanding of things though.