FileMaker Pro VS git-sizer

• Ease of Use
  FileMaker Pro features a highly intuitive design with drag-and-drop functionality, making it accessible for users with limited technical skills.
• Cross-Platform Compatibility
  The software is compatible with both macOS and Windows, offering flexibility for users operating on different systems.
• Customizability
  Users can create highly customized databases suited to their specific needs, from small business operations to larger enterprise solutions.
• Integration Capabilities
  FileMaker Pro seamlessly integrates with various external applications and services, including APIs, AppleScript, and ODBC/JDBC connectivity.
• Rapid Development
  The platform enables quick development and deployment of database solutions, which can be a time-saver for businesses needing immediate solutions.
• Cloud Hosting
  Claris' cloud hosting option provides secure, centralized access to your databases from anywhere, enhancing collaboration and remote work.
• Strong Community Support
  A large, active community of users and developers provides extensive resources, forums, and third-party plugins to extend functionality.

Possible disadvantages

• Cost
  FileMaker Pro can be relatively expensive, especially for small businesses or individual users, considering the licensing fees.
• Limited Scalability
  It may become less efficient for extremely large, enterprise-level databases, making it less suitable for very high-scale operations.
• Learning Curve for Advanced Features
  While basic functions are easy to learn, mastering advanced features and scripting can be complex and may require comprehensive training.
• Proprietary Nature
  FileMaker uses its own proprietary technology, which can make integration with some other systems and platforms more challenging compared to open-standard solutions.
• Performance Issues
  Some users report performance slowdowns when dealing with very large datasets or numerous concurrent users.
• Mobile App Limitations
  The mobile version, FileMaker Go, may have limitations compared to the desktop version, particularly in terms of functionality and complexity.

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

No analysis of FileMaker Pro yet.

Tracking FileMaker Pro 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