• MonkeMischief@lemmy.today
    0·
    6 days ago

    Man I get paranoid about synchronization programs for this very reason. There’s usually some turnkey easy-mode enabled as soon as you first launch that’s like:

    “Hey you wanna back up your entire NAS to your phone?! That’ll be fun, right?!”

    And you’re like “…No.”

    And then it wants to obliterate everything so it’s all “synchronized”, often it’s not easy to find a “No, stop, don’t do anything at all until I configure this.” Option.

    iTunes was SO BAD about this.

    Syncthing is the least-bad sync software I’ve ever run. It’s got some footguns but it’s still brilliant.

    I would imagine there’s still ways to back up version controlled software right?

  • MystikIncarnate@lemmy.caEnglish
    0·
    6 days ago

    While I have some sympathy for anyone who loses months of work, as an IT administrator by day, all I have to say about their lack of backups, and lack of RTFM before messing with shit is:

    HAHAHAHAHAHAHA HAHAHAHAHA. you got what you deserved fucker. GL.YF.

  • DelightfullyDivisive@lemmy.worldEnglish
    0·
    6 days ago

    I’m sure that the “three months of work” was completely shit code. Anybody who is unfamiliar with source control (or even backups!) is prone to making stupid mistakes. Republican voters are likely to have a similar experience over the next 4 years.

  • Phoenix3875@lemmy.world
    0·
    6 days ago

    Reminds me of a hilarious bug in early GHC: https://gitlab.haskell.org/ghc/ghc/-/issues/163

    The compiler will delete your source file if there’s any compile error. And the user complained only by sending a very polite email to report this bug. Simon Peyton Jones mentioned it in one of his talks and I still find it quite hilarious till this day.

  • AwkwardLookMonkeyPuppet@lemmy.worldEnglish
    0·
    6 days ago

    Why are they messing with the source control options when they’re not using source control? Perhaps learn about stuff before you start clicking buttons and performing delete operations on your super critical files?

  • مهما طال الليل@lemm.ee
    0·
    6 days ago

    So VS Code isn’t just slow and bloated, it also deletes your files. So glad I was turned off by its excessive memory consumption and deleted it before it deleted my files.

    Edit: also why I only ever used git from the command line, I never found a git UI that is easy to understand, and never trusted them.

    • hperrin@lemmy.world
      0·
      6 days ago

      You think VS Code is slow and bloated? What do you use?

      Also, on several occasions I’ve had VS Code help me recover accidentally deleted files, because the editor keeps the file in memory, regardless of if it disappears on disk (like most editors).

      • مهما طال الليل@lemm.ee
        0·
        6 days ago

        What do you use?

        Either an IDE like Visual Studio or Xcode or a text editor like Notepad++, Vim or nano, it depends. I also use Android Studio but I hate it.

    • auzy@lemmy.world
      0·
      6 days ago

      It’s really not slow or bloated. There’s a reason it’s so popular (even in Linux)

      If it’s running slow, maybe it’s time to check your computer…

      I literally had to use it to load 100 git projects simultaneously recently

    • AwkwardLookMonkeyPuppet@lemmy.worldEnglish
      0·
      6 days ago

      No it doesn’t delete your files. Hombre from the post told it to delete his files and was then shocked when it did. It even warms you that it’s about to delete your files. Then on top of that, post person wasn’t even using source control, so they can’t get their files back. Don’t mess with the source control options if you’re not using source control. Don’t just randomly click buttons without reading if your project files are super critical. Don’t only have a single version of your entire project in a single place on one computer. This person obviously has no idea what they’re doing, which is fine, but they don’t belong anywhere near a 5000 file project.

        • AwkwardLookMonkeyPuppet@lemmy.worldEnglish
          0·
          6 days ago

          Why? There’s a full git log of the files. It’s trivial to get them back. That brings us to the “don’t use the source control tab if you’re not using source control” point.

      • مهما طال الليل@lemm.ee
        0·
        6 days ago

        Two things can be right at the same time. I remember when I used to run VS6, IE and WinAmp in 128MB with KBs to spare. Even today, proper VS is a much better product than VSCode while being a full fledged IDE and not just a glorified text editor.

        • auzy@lemmy.world
          0·
          6 days ago

          Vscode is an ide

          If vs6 is so great, feel free to use it

          It’s also about productivity, Notepad uses less ram, but is not productive. This runs fine on any machine really

          And the point of ram is to be used… You can’t check the ram usage and simply assume it’s bloated, because most apps also cache too. RAM is meant to be used

    • JackbyDev@programming.devEnglish
      0·
      6 days ago

      Go read the actual thread. There was a bug someone found that files you have in there that aren’t even associated with git still get deleted. I’m not entirely convinced this was the poster’s fault.

      • bitwolf@sh.itjust.worksEnglish
        0·
        5 days ago

        I did read the whole thread. I also referenced the resolution further down the comment thread.

        They’ve adjusted the error message to be abundantly clear after the fact.

      • Scoopta@programming.dev
        0·
        6 days ago

        It’s not a bug, it’s intentional. They consider changes to be any change since the last commit including in untracked files. They did update it to make this behavior a lot more obvious though.

          • Scoopta@programming.dev
            0·
            6 days ago

            Yes, honestly this situation reminds me a lot of the LTT trying Linux and destroying his system by installing steam despite apt warning him in the best way it really could that he probably didn’t want to do that. Sure the package shouldn’t have been in that state in a stable distro but shit happens. It goes to that point of, users will go through great lengths to achieve the end goal blindly jumping past warnings on the way no matter how dire they might be.

      • zalgotext@sh.itjust.works
        0·
        6 days ago

        If you use git and understand that VSC’s source control stuff is just a thin wrapper around git, you should understand what “discard all changes” means

          • zalgotext@sh.itjust.works
            0·
            6 days ago

            I’m not claiming that “discard” is a git action. I’m claiming a git user should understand what’s meant by the phrase “discard changes”. Run git status in a repo that has changes in the working directory. In the resulting output, there’s a message:

            Changes not staged for commit:
    (use "git add <file>..." to update what will be committed) 
    (use "git restore <file>..." to discard changes in working directory)
        ...

            The phrase “discard changes” is used consistently in git’s output.

      • bitwolf@sh.itjust.worksEnglish
        0·
        6 days ago

        I just tried right now to get the exact message.

        Are you sure you want to DELETE foo?
        This is IRREVERSIBLE!
        This file will be FOREVER LOST if you proceed.

        The confirmation button even says Delete File…

        User error.

    • SPRUNT@lemmy.world
      0·
      6 days ago

      Man who clicks confirmation for leopards to delete his work is angry and surprised when his work is deleted.

  • kamen@lemmy.world
    0·
    6 days ago

    I agree with the “learn the CLI”, but to newcomers I’ll also suggest to look at the IDE/editor’s output channel - if there’s GUI for Git, there are also most likely logs for what’s happening under the hood - even if a little noisy, it can be a good learning resource. And of course if you’re learning and unsure of what’s happening (with the CLI or through a GUI), do so in a non-destructive manner (by having proper backups).