https://arm.jonpalmisc.com/latest_aarch64/index.html (Just the base instruction set for the latest ARM architecture without any extensions)

https://en.wikipedia.org/wiki/RISC-V_instruction_listings (Look at just the I instructions for the base instruction set without the extensions)

That's... debatable. While the R in ARM does stand for RISC, there are way too many instructions in the base instruction set of the latest ARM ISA for me to comfortably call it a RISC architecture, especially when compared to RISC-V, which has an extremely slim base instruction set comparatively.

  • source
  • parent
  • context
  • [–] 6 points 1 month ago (2 children)

    when I tell them they thank me for my time and keep doing it

    I remember one of my first programming jobs in the mid-90s for an internet startup. I was the sole developer and I had absolutely no idea what I was doing, but I was treated like a rock star and thought of myself as one. My bosses called in a high-priced consultant to review my (Visual Basic) code and I still remember his report vividly. He ripped me a new one and I was highly offended and justified everything I had been doing to my bosses and they agreed with me and never talked to the consultant again. I'd like to find that guy again and say "yeah, you were spot on" but he was in his 50s at the time and this was 30 years ago, so I assume he's dead. One of the fortunate ones who never had to deal with AI, just with shitty noob programmers.

  • source
  • parent
  • context
  • [–] 4 points 1 month ago

    I'm in the long process of sorting out tons of duplicate files too, and I'm using krokiet, which is the new GUI version of czkawka. It's not perfect, but it is the best tool I have found so far.

  • source
  • [–] 8 points 1 month ago (3 children)

    I had a coworker once who had come to our C# project from the Java world. Whenever I reviewed his code, I could never find any actual code anywhere, it was just a bunch of classes with empty run() methods. But everything he wrote functioned perfectly, so I dunno. It's the closest I've ever come to feeling like I was being visited by a superior extra-dimensional being.

  • source
  • parent
  • context
  • [–] 8 points 1 month ago* (last edited 1 month ago)

    +1 for czkawka, it was the only thing that worked for my lazy brain. It also works for exact duplicates.

    No matter the method though, the way OP describes it it's still going to be a slog. At least it was for me when I was in a similar situation.

  • source
  • parent
  • context
  • [–] 9 points 1 month ago (4 children)

    I will be abusing the fuck outta this once it's forked and adapted for non-gaming purposes to avoid shitty electron apps forever. Most electron apps have Android equivalents that run way better and eat far less RAM. Can't wait ☺️

  • source
  • parent
  • context
  • [–] 8 points 1 month ago

    rsync has a --dry-run / -n flag that would tell you which files would be synced. Combined with --archive /-a it runs recursively.

    That said, it's assumes file paths are matching between source and destination, so if things are scattered, it might not work well.

    If you're really scattered, I'd consider using a simple python script to walk directories and create a json file with results (maybe the sha256 for key and filename, size, absolute path, and created/modified stamps as fields). Then when you hit a duplicate key, you can dump the results and prompt a delete.

    Or something. I'm just spit balling here.

  • source
  • [–] 13 points 1 month ago (1 child)

    Easy question, hard answer.

    If you want the easy answer: one new folder, look through everything you want to keep, and copy it to the new folder. Then delete the rest.

    For a quick deuplication, fdupes will find exact duplicates. Read the man page, because there's a cache option you probably want to use.

    If there are inexact duplicates, like photos or videos, use tools like czkawka.

  • source
  • [–] 2 points 1 month ago (2 children)

    I'm sure someone else has a better method, but I'd just use whatever file manager you have to consolidate everything into one folder and let the file system flag any dupes.

    Have ten movie folders on a bunch of different drives? Pick the biggest one, attempt to move the next biggest one into it, ignore all dupes, repeat.

    Again, though, there's probably a better way

  • source
  • [–] 4 points 1 month ago (1 child)

    I'm only familiar with CLI tools but at least for smaller directories diff works well. Say you have a backup directory and you want to see how it differs from a source directory:

    diff -rq /source/directory /backup/directory

    Another trick is to use find to look for a unique file to see where, if at all, it's backed up:

    find /backup/directory -name unique-file-name.jpg

  • source
  • view more: ‹ prev next ›