Git has this problem only as far as the developer's storage of the history of all files is concerned. That "junk" doesn't remain in the final program. You can

Git has this problem only as far as the developer's storage of the history of all files is concerned. That "junk" doesn't remain in the final program. You can have a decades-old git repository containing hundreds of MBs of files, but output a 2kB program. Someone correct me, but it sounds like if you had the same thing with a unison project, the actual executable size can only grow?