• FizzyOrange@programming.dev
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    4 months ago

    There are use cases like monorepos where vdm won’t work.

    Erm yeah because the whole point of monorepos is that you don’t use submodules. What?

    Git does track submodule history unlike vdm.

    The history of submodules is tracked in the submodule repo. VDM doesn’t change that.

    It uses them.

    It doesn’t use them any differently to if you had just checked out the submodule standalone. I’m not exactly sure what VDM does (haven’t used it) but that doesn’t seem like a big thing.

    This is not how git submodules or subtrees work.

    No?. Actually that’s not all you need to manage for git submodules - there’s additional hidden state so you can’t just edit that file; you need to use git add/rm. Which is fundamentally the same but worse - this is one of the selling points of the alternatives like VDM. It’s way less confusing.

    Git submodules and subtrees don’t support anything other than git remotes.

    So? Alternatives to git submodules don’t need to restrict themselves to its features.

    • lysdexic@programming.dev
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      4 months ago

      Erm yeah because the whole point of monorepos is that you don’t use submodules. What?

      Not true. The whole point of monorepos is that you track everything in a single repo. There is absolutely no requirement or constraint to avoid using specific features of specific VCSs or even package managers.