3 ms·
> is now even faster and safer How fast and safe was it before? Seems to be no way of knowing, as the git history has been blown away, what's up with that?
by WatchDog 3y ago
> is now even faster and safer
How fast and safe was it before? Seems to be no way of knowing, as the git history has been blown away, what's up with that?
- tptacek 3y agoIt's been forked a bunch of times in the past.
- mpixel 3y agoWhich also show only a few commits, initial commit being dump of the project like this one. Anyway, I'm not a fan of this style of using Git, but personal projects are ultimately, personal, to each their own.
- WatchDog 3y agoSure, live and let live, but there is no way I would use a library that doesn't maintain a version history, especially so given the nature of go's non-centralized dependency management system. Even if you pin your dependencies to a particular commit hash, eventually github will garbage collect detached commits, and your project will fail to build.
- bewuethr 3y agoThe Go module proxy would likely keep it around, but I wouldn't feel great about relying on a "proxy only" dependency.