Dropsource VS git-sizer

• Ease of Use
  Dropsource provides a user-friendly drag-and-drop interface which makes it accessible for users with little to no coding experience.
• Cross-Platform Support
  Allows you to create applications for both iOS and Android platforms, increasing the reach of your app.
• Real-Time Testing
  Offers real-time testing tools, which enable users to test their applications on actual devices as they are being developed.
• Pre-Built Integrations
  Provides a variety of pre-built integrations for popular APIs and services, speeding up the development process.
• Generated Code Export
  Enables users to export the auto-generated code, allowing further customizations and modifications as needed.

Possible disadvantages

• Cost
  May be relatively expensive for small startups and individual developers, especially if advanced features or higher tiers are required.
• Limited Customization
  While the drag-and-drop interface is easy to use, it may limit the customization options for experienced developers who require more control over their code.
• Learning Curve
  Despite its ease of use, there is still a learning curve involved, particularly for those entirely new to app development.
• Dependency on Platform
  Relies heavily on the Dropsource platform, which could be a risk if the company changes its pricing, policies, or discontinues service.
• Performance Overheads
  Generated code may not be as optimized as hand-written code, potentially leading to performance overheads in complex applications.

• 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 Dropsource 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