Source-Navigator NG VS git-sizer

• Multi-Language Support
  Source-Navigator NG supports a wide range of programming languages including C, C++, Java, and more, making it versatile for different types of development projects.
• Cross-Platform
  It operates on multiple platforms, including Windows, Linux, and macOS, allowing developers to use the tool irrespective of their operating system.
• Code Navigation
  The tool offers advanced code navigation features, such as call trees, symbol browsing, and source code tagging, which can significantly enhance productivity.
• Open Source
  Being an open-source software, it is free to use and allows for community-driven improvements and customizations.
• Integration
  Source-Navigator NG can be integrated with various build systems and version control systems, facilitating seamless development workflows.

Possible disadvantages

• Outdated Interface
  The user interface is considered outdated by modern standards, which might affect the user experience negatively.
• Limited Documentation
  The available documentation is limited and can be challenging for new users to get started with the tool.
• Performance Issues
  Some users have reported performance issues when handling very large codebases, potentially slowing down development.
• Steep Learning Curve
  Due to its comprehensive set of features, it has a steep learning curve, which might deter less experienced developers.
• Community Support
  Although it is open-source, the community support is not as extensive as that of other more popular development tools.

• Comprehensive Repository Analysis
  git-sizer analyzes many different dimensions of a Git repository including commit count, tree size, blob size, history depth, and reference counts, providing a holistic view of repository health and potential scaling issues.
• Easy to Use
  The tool is simple to run with minimal setup—just execute it within a git repository—and it produces clear, human-readable output that highlights potential problem areas without requiring complex configuration.
• Identifies Performance Bottlenecks
  It helps identify specific issues that could degrade Git performance, such as excessively large blobs, deep history, large trees, or too many references, which is valuable before migrating or scaling repositories.
• Open Source and Maintained by GitHub
  Being an official GitHub project, it benefits from credibility, community trust, and ongoing maintenance, and it is well documented with clear explanations of what each metric means.
• Useful for Pre-Migration Checks
  It's particularly helpful for teams migrating repositories to new platforms or consolidating repos, as it flags potential issues that could cause problems during migration or with hosting providers' limits.

Possible disadvantages

• No Automatic Remediation
  git-sizer only identifies and reports issues but does not offer any built-in tools or automated processes to fix problems like large blobs or excessive history depth—users must use separate tools like BFG Repo-Cleaner or git-filter-repo.
• Output Can Be Overwhelming for Beginners
  While detailed, the output includes many metrics and threshold levels that may be confusing for users unfamiliar with Git internals, requiring some learning curve to fully interpret results.
• Limited to Local Analysis
  The tool analyzes a local clone of the repository, so it requires users to have a full local copy of the repo (or at least enough history) to get accurate results, which can be time-consuming for very large repositories.
• No Real-Time Monitoring
  It functions as a one-time analysis tool rather than providing continuous or real-time monitoring of repository health, requiring manual reruns to track changes over time.
• Command-Line Only Interface
  The tool lacks a graphical user interface, which may be less accessible for users who prefer visual dashboards or are less comfortable with command-line tools.

Tracking Source-Navigator NG since Mar 2021.

• how to keep github repos small?

  Also there’s a cool project from GitHub you can use to help understand the size of git’s objects in your git repo https://github.com/github/git-sizer. This might help you determine what the best cloning strategy could be. Source: almost 5 years ago