poll.ly VS git-sizer

• Ease of Use
  Poll.ly has a straightforward and user-friendly interface, making it easy for users to create and participate in polls without any technical knowledge.
• Free to Use
  Poll.ly is free, which is a significant advantage for individuals and small organizations looking to gather opinions without incurring costs.
• No Signup Required
  Users can create and participate in polls without requiring a sign-up, which simplifies the process and preserves user anonymity.
• Real-Time Results
  Polls on Poll.ly can provide real-time results, which is beneficial for live events and situations where immediate feedback is needed.

Possible disadvantages

• Limited Features
  Poll.ly offers basic functionality and lacks advanced features like detailed analytics, complex question types, and integrations with other platforms.
• No Branding Options
  Poll.ly does not offer customization or branding options, which can be a drawback for businesses looking to maintain a consistent brand presence.
• Security Concerns
  Since no sign-up is required, there might be concerns regarding the security and authenticity of the poll responses, as anyone with a link can vote.
• Lack of Mobile Optimization
  Some users have reported that Poll.ly is not fully optimized for mobile devices, which can be an inconvenience for participants responding via smartphones.

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

• I hate society

  Neither am I - I'm one of the few people on this subreddit - tho, maybe not so few after all - who thinks that capitalism can still be salvaged, e.g. Via a Universal Basic Income. Yet here we are, constantly arguing with each other. Source: over 5 years ago

• 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