On the Issues VS git-sizer

• Comprehensive Political Coverage
  On the Issues provides a wide range of information on various political figures and their stances on numerous issues, allowing users to gain a holistic view of their positions.
• Non-Partisan
  The platform aims to present information without political bias, making it a valuable resource for individuals seeking balanced insights into political stances across party lines.
• Issue-Based Categorization
  The website categorizes politicians' views by issues, making it easy for users to find concise summaries of where politicians stand on specific topics.
• Historical Context
  On the Issues often provides historical voting records and statements from politicians, helping users understand the evolution of a politician's positions over time.

Possible disadvantages

• Information Overload
  The site hosts a vast amount of data, which can be overwhelming for some users trying to sift through extensive information to find relevant details.
• Interface and Usability
  The website's design may feel outdated and less intuitive, potentially hindering user experience and ease of navigation.
• Limited Context
  While aiming for brevity, the summaries may sometimes lack the necessary context or nuance to fully understand a politician's stance on complex issues.
• Data Timeliness
  There might be delays in updating information, which could lead to outdated data being presented, especially during rapidly changing political climates.

• 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 On the Issues yet.

• Sean Strickland was never my friend

  Seems a bit different. I used to buy into the "both are wrong and on the same team" theory. That is just an incorrect and false narrative. We elect our representatives... There is a place we can look at their past voting records, etc.... Source: over 3 years ago

• Acceptance rates should be banned

  I agree. We all need to look into voting records, etc. Look who the best person is to put in office to work for us. I use ontheissues.org as I am sure there are other sites and articles as well. The website I posted lets you know... Source: over 3 years ago

• Why we need to vote.

  Ontheissues.org and ballotpedia.org. Source: almost 4 years ago

View more

• 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