3 ms·

I don't get the opposition to submodule. imho it's fine, there are limited options with it, so limited chance it may go wrong. some suggested package manager,

I don't get the opposition to submodule. imho it's fine, there are limited options with it, so limited chance it may go wrong. some suggested package manager, which imho is another layer of dependency, e.g. in Python, it always takes me some extra seconds to figure out which package manager I'm supposed to use, and it's constantly evolving. end of day it's up to which one you are most familiar with.

sshine 2y ago
Submodules are the feature you discover someone pulled in when things don't work, and after a bit of digging, you realize it's because the submodule wasn't initialized, and it didn't say so anywhere. I suspect the opposition to submodules comes from the poor (manual) integration. As someone suggested in another thread, they ought to auto-recurse by default. But I don't think that's going to happen, either. Maybe something like direnv where it tells you about the unloaded submodule once you enter the repository. Except that won't work for IDEs.
- deleted 2y ago
  [deleted]
nobodywillobsrv 2y ago
I think one problem is that submodules are kind of over-kill in situations where what you really want is to have separate repos for various reasons but one way of pulling them all in at once. You could make a script with the origins etc but then you put than in a repo and then ... I use them in my personal projects and have a sprawling mass of crazy. It "works" but it's a pain and I have scripts to recursively crawl through and basically do 'git pull' everywhere or 'git push'. So if you end up using submodules when you don't really care about versioning the sub-repos, I think you end up feeling a bit of an idiot like me. But it's a pain to reverse.
sureIy 2y ago
Same here. I used it and set it up once and had no issues personally, but only after documenting how to deal with it exactly. It's just a rare feature so people don't know how to deal with it, so they just hate it. Once you figure out the 5 commands you will need you're golden.
dig1 2y ago
My impression of this opposition (and hate) is that people don't read the docs and expect submodules to bend to their vision of how submodules should work. Because of that, we have multiple similar but not the same "submodule" implementations: git-submodule, git-subtree, git-subrepo...

sshine 2y ago

Submodules are the feature you discover someone pulled in when things don't work, and after a bit of digging, you realize it's because the submodule wasn't initialized, and it didn't say so anywhere. I suspect the opposition to submodules comes from the poor (manual) integration. As someone suggested in another thread, they ought to auto-recurse by default. But I don't think that's going to happen, either. Maybe something like direnv where it tells you about the unloaded submodule once you enter the repository. Except that won't work for IDEs.

deleted 2y ago
[deleted]

nobodywillobsrv 2y ago

I think one problem is that submodules are kind of over-kill in situations where what you really want is to have separate repos for various reasons but one way of pulling them all in at once. You could make a script with the origins etc but then you put than in a repo and then ... I use them in my personal projects and have a sprawling mass of crazy. It "works" but it's a pain and I have scripts to recursively crawl through and basically do 'git pull' everywhere or 'git push'. So if you end up using submodules when you don't really care about versioning the sub-repos, I think you end up feeling a bit of an idiot like me. But it's a pain to reverse.

sureIy 2y ago

Same here. I used it and set it up once and had no issues personally, but only after documenting how to deal with it exactly. It's just a rare feature so people don't know how to deal with it, so they just hate it. Once you figure out the 5 commands you will need you're golden.

dig1 2y ago

My impression of this opposition (and hate) is that people don't read the docs and expect submodules to bend to their vision of how submodules should work. Because of that, we have multiple similar but not the same "submodule" implementations: git-submodule, git-subtree, git-subrepo...