3 ms·

Seems like the main repository ("arcadia") isn't there.

EMIRELADERO 4y ago
Looked around and it seems like arcadia is a sort of VCS on top of git/a build system? https://github.com/yandex/CMICOT/blob/master/.arcadia.root https://github.com/yandex/CMICOT/blob/master/.arcadia.root
- pshirshov 4y ago
  When I've been there arcadia was the primary SVN monorepo where everything was stored (and built by custom flavour of cmake). From what I heard it's still SVN and git was completely eradicated in the company.
  - 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 ago
      Yandex 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 ago
      Google 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 ago
        While 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 ago
      In case of centralized development git creates too much friction, svn works better there.
    - pshirshov 4y ago
      git 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.

Looked around and it seems like arcadia is a sort of VCS on top of git/a build system? https://github.com/yandex/CMICOT/blob/master/.arcadia.root https://github.com/yandex/CMICOT/blob/master/.arcadia.root

pshirshov 4y ago
When I've been there arcadia was the primary SVN monorepo where everything was stored (and built by custom flavour of cmake). From what I heard it's still SVN and git was completely eradicated in the company.
- 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 ago
    Yandex 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 ago
    Google 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 ago
      While 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 ago
    In case of centralized development git creates too much friction, svn works better there.
  - pshirshov 4y ago
    git 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.