News for hackers. Stuff that matters.
Re:Rsync, GUIs, power, control, design, and decisions by tonyedgecombe on Tuesday July 09, 2019 @12:24PM (#20393461)
rsync is one of those tools that I use so infrequently that I’d rather have a good GUI than have to relearn the command switches every time I use it.
Re:Rsync, GUIs, power, control, design, and decisions by SkyMarshal on Tuesday July 09, 2019 @12:37PM (#20393620)
Or just script it, include good comments explaining why you used all the switches you used, and back up the scripts to your favorite backup service. Available everywhere and explained well so you don't forget why you choose the switches you did.
Re:Rsync, GUIs, power, control, design, and decisions by dvtrn on Tuesday July 09, 2019 @12:45PM (#20393744)
Good suggestion here.

I created a single serving Ansible docker image with a couple of playbooks for this very purpose --devs were asking frequently to pull schemas or dump from various data sources internally "Hey I forgot the command to do this, what was it again?".

Eventually I gave them a Dockerfile, wrote up some documentation on how to change hosts in the run command if they so desired, questions all but stopped immediately, and the devs loved it.

I now get a new question "hey, can you make one of those but to do this?"

"Sure, here's a playbook for it, put this in that directory on your local machine and it'll be available in the container". Combined with dynamic host inventories, it's made me a few friends lol

Re:Rsync, GUIs, power, control, design, and decisions by mixmastamyk on Tuesday July 09, 2019 @12:48PM (#20393802)
And in the scripts, use the long-form flags, so many comments are unnecessary.
Re:Rsync, GUIs, power, control, design, and decisions by floatboth on Tuesday July 09, 2019 @01:00PM (#20393954)
Yeah. Though rsync is not the most option-rich program ever. What really needs GUI is... ffmpeg! :)
Re:Rsync, GUIs, power, control, design, and decisions by Wowfunhappy on Tuesday July 09, 2019 @01:11PM (#20394127)
There are lots and lots of ffmpeg GUIs, the problem is that IMO, all of them are either (1) not powerful enough or (2) more difficult to use than just the command line.

The first problem may, of course, be a non-issue depending on what you need to do.

Re:Rsync, GUIs, power, control, design, and decisions by gmfawcett on Tuesday July 09, 2019 @01:34PM (#20394426)
Someone with a sufficient itch (and some Elisp skills) could probably do for ffmpeg what the Magit team did for Git. Git's another program with a litany of options, and Magit does an outstanding job of covering them with an easy-to-use interface.

https://magit.vc/manual/magit/

Admittedly the ffmpeg bar is probably higher, esp. given that ffmpeg can be configured and built a couple dozen different ways.

Re:Rsync, GUIs, power, control, design, and decisions by marcosdumay on Tuesday July 09, 2019 @02:13PM (#20394901)
Handbreak is a really good GUI for ffmpeg. The problem is that i (with its ~20 different windows) supports only one use case of the tool.
Re:Rsync, GUIs, power, control, design, and decisions by aidenn0 on Tuesday July 09, 2019 @03:17PM (#20395556)
I'd love to just make a GUI for generating ffmpeg filter graphs. The MS SDK had a directshow filter graph editor (graphedit i think it was called?) that was quite pleasant to use back in the day.
Re:Rsync, GUIs, power, control, design, and decisions by Fnoord on Tuesday July 09, 2019 @02:24PM (#20395045)
ffmpeg needs a GUI? Nah, you just make aliases or script it as this comment already described for Rsync [1] [1] https://news.ycombinator.com/item?id=20393620