I find this to be one of the most useful features of git submodules. I can easily just cd into the module and do whatever related work I need to do there and then commit to both projects when I'm ready.
Co-workers who have moved from svn to git have had no trouble understanding and working with git submodules.
2. Git submodules are occasionally used, but svn externals is something I'd never seen used back when I was on svn using teams.
To be complained about, something must be known about, and I think for most developers, svn externals isn't known about
For example, in the project that I'm working on now, I have refined the app's "business logic" to an SPM module that I integrate, through GitHub.
The idea is that I don't change the logic, and I enforce that, by using it as an SPM module.
However, every now and then, I encounter a bug in this module, or I find the need to add something to its API. When that happens, I need to exclude the module from the dependency list in the project, include it directly, as a local link, and work on it that way. Committing is a separate task from the main app (Xcode allows aggregate commits, but Xcode's Git integration is so poor, that I don't use it).
It actually works well. A submodule would also work well, with more Git integration, but the drawbacks far outweigh the advantages.
I would also agree with OP that submodules are horrible. Source: I have to deal with them everyday in my company's repo and they cause issues pretty much every time I pull, switch branches, merge/rebase, etc.
IMO, one of the MAIN issues with submodules is that there isn't an actual FILE, checked in the repository, and understood by Git, that lists the hash of all the submodules used. So diffs and PRs on Github, git, etc. don't show the actual changes in a way that we're already used to with files.
- committing a commit hash from a foreign repository in a text file (.gitmodules), along with
- some convenience tooling to check out that repository's tree at that commit in a subdirectory.
It is useful exactly when you want both of those things at once. Wanting the first is common enough, it's wanting the second that's more rare.
For example, you wouldn't submodule a Rust dependency, because you get what you want by committing the hash to a text file (Cargo.toml), and tooling to check it out in a subdirectory of your project gets you nothing.
I think the error the Git project made with submodules is trying to make them transparent, i.e., allowing you to use Git inside the submodule checkout. This is basically never a good idea; it is understandable that people get confused trying it (the thing they are trying to do is inherently confusing; if you have already been traumatized by submodules, imagine doing it with Cargo.toml or similar - it would be a mess!).
You probably don't want submodules. But they're useful, and not at all broken or poorly specified.