Dartfish Mobile VS git-sizer

• Comprehensive Video Analysis
  Dartfish Mobile offers robust video analysis tools that allow users to break down footage for detailed examination, providing features such as slow motion, tagging events, and adding annotations.
• Accessibility
  The mobile application enables users to perform video analysis on-the-go, providing flexibility and convenience for capturing and reviewing footage directly from mobile devices.
• Cloud Integration
  With seamless cloud integration, Dartfish Mobile allows for easy storage, sharing, and collaboration on video projects across teams and devices.
• User-Friendly Interface
  The intuitive interface ensures that both new and experienced users can navigate and utilize the application features effectively.

Possible disadvantages

• Cost
  While the app serves professional needs well, Dartfish Mobile can be expensive, particularly for individual users or small organizations when considering subscription plans and additional features.
• Learning Curve
  Despite its user-friendly design, the range of tools and features may require time for new users to fully understand and utilize effectively.
• Device Compatibility
  There might be limitations on performance and functionality due to varying capabilities of mobile devices, particularly with older models.
• Feature Limitations Compared to Desktop
  The mobile app may not offer all the advanced features available in the full desktop software, potentially limiting the depth of analysis possible on mobile devices.

• 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 Dartfish Mobile since Aug 2022.

• 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