The problem with submodule is not when you add them, but when use remove them, you have to clean a hell of things. Further more, if submodule is written in different language from the one my project uses, I have to recompile them. I use submodule only when I have no good package manager option.
Different Languages? Recompile?? Package Manager?? None of these are related to Submodules.. I think you may confusing what submodules are for. But I will agree, there are times when removing submodules or switching between branches that have/done have them are a bit of a pain. You may be better off using SmartGit GUI. It does make 99% of all the headaches of Submodules vanish. (Except for the removing part). But that is mainly because git itself is bad at them.
1. "Package manager is not related to git-submodule" What do you use submodule for, if not for modules - the very thing that package managers are designed to work with. Git is not designed to work with modules. 2. "Different Languages? Recompile?" Have you ever use a C/C++ lib inside a Python or a NodeJS project? If you are using their package managers (pip, npm), chances are the package manager will download precompiled binaries and link them for you. But if you're using submodule, good luck with compiling and linking the libs manually. 3. "I really don't know what people's problem with it is!" vs "but mainly because git itself is bad at them" Oops. What should I follow?
1: git submodule is for putting another repo (at a certain commit) inside another repo. FULL STOP. What is contained in those repos is entirely up to you. Are you confusing submodules as a package manager / module manager? Seems you may be caught up on the name.. Think of them as SubRepos instead of SubModules.. Maybe that will help? 2: git doesn't care what languages go inside the repo. Could be a collection of images for all it cares. So language is not a factor. If you are trying to mix languages and stuff up, that is a fault on you. Not git. Git just manages what ever file you place in a folder. 3: NO idea what you mean by follow.
1. Again (because you didn't really answer my question), why would you put another repo inside a repo, if not to be used as a package/module? If you just want a directory, why not just copy that repo into your repo? 2. I agree that Git doesn't care what language is inside the repo, and Git doesn't have to. Which is why using submodule is a problem. Package manager solve all of this, seamlessly. 3. Your first comment said that you really don't know what the problem with git-submodule contradicts with your reply that said you're well aware what is the problem and why is that.
I like Submodules!! I really don't know what people's problem with it is!
The problem with submodule is not when you add them, but when use remove them, you have to clean a hell of things. Further more, if submodule is written in different language from the one my project uses, I have to recompile them. I use submodule only when I have no good package manager option.
Different Languages? Recompile?? Package Manager?? None of these are related to Submodules.. I think you may confusing what submodules are for. But I will agree, there are times when removing submodules or switching between branches that have/done have them are a bit of a pain. You may be better off using SmartGit GUI. It does make 99% of all the headaches of Submodules vanish. (Except for the removing part). But that is mainly because git itself is bad at them.
1. "Package manager is not related to git-submodule"
What do you use submodule for, if not for modules - the very thing that package managers are designed to work with. Git is not designed to work with modules.
2. "Different Languages? Recompile?"
Have you ever use a C/C++ lib inside a Python or a NodeJS project? If you are using their package managers (pip, npm), chances are the package manager will download precompiled binaries and link them for you. But if you're using submodule, good luck with compiling and linking the libs manually.
3. "I really don't know what people's problem with it is!" vs "but mainly because git itself is bad at them"
Oops. What should I follow?
1: git submodule is for putting another repo (at a certain commit) inside another repo. FULL STOP. What is contained in those repos is entirely up to you. Are you confusing submodules as a package manager / module manager? Seems you may be caught up on the name.. Think of them as SubRepos instead of SubModules.. Maybe that will help?
2: git doesn't care what languages go inside the repo. Could be a collection of images for all it cares. So language is not a factor. If you are trying to mix languages and stuff up, that is a fault on you. Not git. Git just manages what ever file you place in a folder.
3: NO idea what you mean by follow.
1. Again (because you didn't really answer my question), why would you put another repo inside a repo, if not to be used as a package/module? If you just want a directory, why not just copy that repo into your repo?
2. I agree that Git doesn't care what language is inside the repo, and Git doesn't have to. Which is why using submodule is a problem. Package manager solve all of this, seamlessly.
3. Your first comment said that you really don't know what the problem with git-submodule contradicts with your reply that said you're well aware what is the problem and why is that.
first ten minutes absolutely for nothing....
This guy needs to move the mic away from his mouth