3 ms·
This is pretty interesting to me. Usually companies will gradually switch over to git. This is the first time I've heard of a company using git and ditching it
by EMIRELADERO 4y ago
This is pretty interesting to me. Usually companies will gradually switch over to git. This is the first time I've heard of a company using git and ditching it in favor of older technology.
- ilyaluk 4y agoYandex used (maybe still using) SVN monorepo named Arcadia for most of the source code. As it became too big, they developed an in-house VCS called Arc and were switching to it; there is more context in a presentation about Arc (2020), transcript/recording in Russian[1] I could assume that this is the leak of Arcadia, and each archive roughly contains one top-level folder. [1]: https://habr.com/en/company/yandex/blog/482926/ https://habr.com/en/company/yandex/blog/482926/
- aflag 4y agoGoogle also uses something close to SVN and explicitly avoids git. I don't think there's any sense of progression between the two. I think it comes down to which one fits your processes better.
- mdaniel 4y agoWhile reasonable people can discuss how "close to SVN" Perforce is, my understanding is that Google was using Perforce for the longest time, or a tool modeled very closely upon it
- GoblinSlayer 4y agoIn case of centralized development git creates too much friction, svn works better there.
- pshirshov 4y agogit is inefficient when you need to handle a huge monorepo where just one checkout weights 66 GiB and the history is measured in tens of terabytes. The other problem not addressed by git was the support of per-directory permissions.