Curious Expedition VS git-sizer

• Unique roguelike exploration theme
  Curious Expedition offers a distinctive blend of roguelike mechanics with a 19th-century exploration setting, allowing players to lead expeditions into uncharted territories with famous historical figures like Darwin, Earhart, and Lovecraft. This thematic combination feels fresh and engaging.
• High replayability
  Thanks to procedurally generated maps, randomized events, and a wide roster of explorers with different perks and abilities, each playthrough feels different. The roguelike nature means permadeath and unpredictable outcomes keep players coming back for more.
• Engaging risk-reward decision making
  The game constantly presents meaningful choices—whether to loot a sacred shrine, push deeper into dangerous territory, or manage dwindling sanity and supplies. These decisions create genuine tension and make every expedition feel like a high-stakes adventure.
• Charming pixel art style
  The game features a beautifully crafted pixel art aesthetic with detailed environments and character sprites that evoke a sense of classic adventure and complement the retro exploration theme perfectly.
• Accessible yet deep mechanics
  While the game is easy to pick up and understand on the surface, there is considerable strategic depth in managing resources, party composition, combat dice mechanics, and navigating random events, appealing to both casual and hardcore strategy fans.

Possible disadvantages

• Heavy reliance on RNG
  Many outcomes in the game are determined by random number generation, from combat dice rolls to event results. This can sometimes feel unfair, as a run can be ruined by a string of bad luck rather than poor decision-making, which may frustrate some players.
• Repetitive over time
  Despite procedural generation, the pool of events, encounters, and biomes can start to feel repetitive after many hours of play. Experienced players may find that the novelty wears off as they encounter the same scenarios repeatedly.
• Shallow combat system
  The dice-based combat system, while initially interesting, lacks the depth and variety needed to stay engaging over long periods. Combat encounters can feel simplistic and overly luck-dependent compared to other roguelikes.
• Limited narrative depth
  While the setting is evocative, the game lacks a deep overarching story or rich character development. The historical figures serve mostly as mechanical archetypes rather than fleshed-out characters, which may disappoint players seeking a strong narrative experience.
• Steep difficulty spikes
  The game can present sudden and punishing difficulty spikes, especially in later expeditions. Combined with permadeath and RNG, these spikes can make certain runs feel unwinnable and lead to frustrating dead ends for less experienced players.

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

The Curious Expedition Review

More videos

No git-sizer videos yet. You could help us improve this page by suggesting one.

Tracking Curious Expedition since May 2026.

• 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