3 ms·
Totally... I really had to defend my decision to script my own backups to a friend of mine. He said 'why didn't you just use duplicati like everyone else'. But
by GekkePrutser 6y ago
Totally... I really had to defend my decision to script my own backups to a friend of mine. He said 'why didn't you just use duplicati like everyone else'.
But duplicati is very big and doesn't do exactly what I want to do (which is not backup as such but more like archive). Also this way I had everything in standard formats that I know I can still open in 30 years if I want to. I've been bitten by commercial backup software formats before, had to install a Windows 95 VM to load really old backups :)
I also wrote many mini applications in work that have been used for many years at no cost, eventually being replaced by off the shelf stuff which did much more than we need and as such was much more complicated for the users.
The IT world is really too focused on off the shelf products right now. Homebrew can be a really efficient way too.
- ChrisMarshallNY 6y ago> Homebrew can be a really efficient way too. What's funny, is that a popular package manager for Apple systems is called "Homebrew"[0]. I am a dependency skeptic, but not a full-on "curmudgeon" (although I am often accused of being one). If you can prove that a dependency is the way to go, and I am satisfied with its provenance and support, I'll probably let it in. One of the big problems with a lot of these efforts, is that the documentation is atrocious. It often has a fancy-ass, big-header, scroll-forever Web site, with God-awful information architecture, no ToC or index, and lots of fancy CSS (like video backgrounds -always a win for a documentation page). There's the obligatory "step and repeat" page, with all the logos of every company that has ever sent them an email, and cute, tongue-in-cheek bios of the team, but it can be difficult to find out how to call a function properly. [0] https://brew.sh https://brew.sh