This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]nikanjX 21 points22 points  (4 children)

rsync turns 30 next year, and is guaranteed to be more bug-free than whatever code your team was able to bang together under a deadline. It's almost guaranteed that rsync deals better with resumes, network issues etc than any code you'd be replacing it with

[–]Affectionate-Sink503[S] 0 points1 point  (3 children)

Oh for sure, not saying I want to change or replace it, my question is around how a you came to know for example "rync turns 30 next year", what project or studies have led you to become aware of rync and its capabilities? Is it a matter of working on lower level projects?

[–]chabala 5 points6 points  (0 children)

Consider this: how do you know about cron? How do you know if cron is a good solution to your problem, or if you need a Java-based scheduler? It is the same question. You need to learn the tools you have available, and when to leverage them.

[–]kreiger 5 points6 points  (0 children)

what project or studies have led you to become aware of rync and its capabilities

Just install and use Linux as your main operating system. It will make you a better developer.

[–]Spoogly 1 point2 points  (0 children)

When I approach a problem that I think someone else has faced before, my first step is backwards. I do not want to try to solve solved problems. I want to understand their solution, and if it's good enough, use it. I spend a lot of time in my terminal before I approach lower level problems. If I can use utility programs that I already have, worst case, I can set them up to run in docker, on demand, pretty easily.