The Future of Large Files in Git Is Git

Re:The Future of Large Files in Git Is Git by 1718627440 on Sunday August 17, 2025 @06:41AM (#44930583)

I'm not talking about what needs to be in Git and what not, I mean for git functionality that analyzes the history (git blame), the data needs to be traversible, i.e. available locally, fetching it over the wire will introduce massive latency. You claimed it doesn't need to be.

> All the features you think are associated with the D in DVCS are perfectly accessible to a more centralized tool.

[ Parent | on HN ]

Re:The Future of Large Files in Git Is Git by forrestthewoods on Sunday August 17, 2025 @03:26PM (#44934172)

Git Blame sucks and is far far far far far far worse than Perforce Timelapse View.

You moved the goal posts a little bit. You are correct that if you want to work in a cave with no internet then you do need every bit of data to perform at least some operation. That’s not what the D in DVCS means though.

[ Parent | on HN ]

Re:The Future of Large Files in Git Is Git by 1718627440 on Monday August 18, 2025 @02:15AM (#44937881)

That's exactly what the D means: All the repo data is on every machine, the repo is complete in itself and no repo is any different than the other.

For me connecting to the Internet is very much a choice. Doesn't mean I wouldn't have access if I didn't want to, but why would I need it most of the time?

[ Parent | on HN ]