Git Submodules vs Manual Code Copying

Developers should use Git Submodules when they need to incorporate external libraries, frameworks, or shared components into their main project while keeping those dependencies as separate repositories with their own version history meets developers might resort to manual code copying in scenarios where they lack access to proper version control systems, need to quickly prototype or test code in isolation, or are working in environments with limited tooling. Here's our take.

Git Submodules

Nice Pick

Developers should use Git Submodules when they need to incorporate external libraries, frameworks, or shared components into their main project while keeping those dependencies as separate repositories with their own version history

Pros

• Common use cases include managing third-party dependencies, sharing common code across multiple projects, or working on large, modular applications where different teams maintain separate repositories
• Related to: git, version-control

Cons

• Specific tradeoffs depend on your use case

Manual Code Copying

Developers might resort to manual code copying in scenarios where they lack access to proper version control systems, need to quickly prototype or test code in isolation, or are working in environments with limited tooling

Pros

• However, it should be avoided in production codebases because it increases technical debt, makes bug fixes and updates harder to propagate, and violates DRY (Don't Repeat Yourself) principles
• Related to: version-control, code-reuse

Cons

• Specific tradeoffs depend on your use case

The Verdict

These tools serve different purposes. Git Submodules is a tool while Manual Code Copying is a methodology. We picked Git Submodules based on overall popularity, but your choice depends on what you're building.

The Bottom Line

Git Submodules wins

Based on overall popularity. Git Submodules is more widely used, but Manual Code Copying excels in its own space.