3 ms·
Much love to the author for clearly thinking through. As GIT was to DVCS, and SemVer to individual package versioning, I feel this proposal is "the one true wa
by ramses0 9y ago
Much love to the author for clearly thinking through. As GIT was to DVCS, and SemVer to individual package versioning, I feel this proposal is "the one true way" as a starting point by which all future progress will be judged.
- strkek 9y agoI don't feel like Git is "the one true way" to DVCS though. For example using SHA1 as hashing algorithm doesn't seem like a good idea. Or calculating "packfiles" ad-hoc on clone operations, that's wasteful and makes cloning big repos on unstable connections a PITA. But it's certainly true that Git is the "current best practice" in the DVCS landscape.
- gkya 9y ago> As GIT was to DVCS... ? Git did not create a novel concept. For one, it was written nearly contemporaneously to Mercurial, which is DVCS too and uses a very similar if not identical model. SemVer is a similar story too. It was not like before it people were using /dev/random to number their releases. I really like the fact that Go is catching up in this area, but I fail to see the revolution everybody's talking about here.