bspwm VS git-sizer

• Highly Configurable
  Bspwm is known for its high level of customizability, allowing users to tweak almost every aspect of their window management experience through simple scripts and configuration files.
• Efficient Use of Screen Space
  As a tiling window manager, Bspwm automatically arranges windows in a way that maximizes screen real estate, minimizing overlap and unused space.
• Lightweight
  Bspwm is extremely lightweight, making it suitable for older hardware and systems with limited resources. It does not come with additional software bloat.
• Scriptable with Unix Philosophy
  Bspwm adheres to the Unix philosophy of 'doing one thing well'. It functions without managing keybindings, allowing users to use other programs (like sxhkd) for keybinding management, which offers greater flexibility.
• Active Community Support
  Bspwm has an active community and comprehensive documentation, which helps new users get started and troubleshoot any issues they might encounter.

Possible disadvantages

• Steep Learning Curve
  The configuration process can be complex and overwhelming for beginners. Unlike more mainstream window managers, bspwm requires learning various scripts and commands.
• Lack of GUI Configuration Tools
  Bspwm does not come with graphical configuration tools, which might be inconvenient for users who prefer a GUI for managing settings.
• Sparse on Built-in Features
  Since bspwm follows the Unix philosophy closely, it lacks many built-in features and utilities that other window managers might offer. Users need to set up additional tools for tasks such as wallpaper management or system trays.
• Compatibility Issues
  Some applications that expect a floating window manager might not work well with bspwm, requiring extra configuration or using alternative software.
• Limited Out-of-the-box Experience
  Bspwm does not come with a pre-configured environment, which can be a disadvantage for users looking for a ready-to-use experience out of the box.

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

Switching To Bspwm - Initial Thoughts

More videos

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

• Top 13 Best Tiling Window Managers For Linux In 2022
  www.hubtech.org · May 2022

  Support for multiple windows, limited support for EWMH, automatic mode for automatically determining the location of app tiles, and configuration and control via messages are among the characteristics of bspwm.

• 13 Best Tiling Window Managers for Linux
  www.tecmint.com · Jun 2020

  bspwm’s features include support for multiple windows, partial support for EWMH, automatic mode for automatically setting the position of app tiles, and it is configured and controlled through messages, among others.

We have no reviews of git-sizer yet. Be the first one to post

• well... thinkpads are awesome

  Over on Linux, I’ve been learning kinda a-lot about linux tools and workflows. I've recently got into window managers, bspwm was my first one and I'm thinking of moving towards a Arch+Hyprland setup in future. Setting it up was way... - Source: dev.to / almost 2 years ago

• What WM should I use?

  Use BSPWM. It supports right clicks by default and its modular. You might want to look for status bars that work with it, slstatus does not work. Good luck, supremacist! Source: over 3 years ago

• What are some OpenSource apps that are the best of their kind?

  I had not heard of bspwm but I am a fan of telling WMs. Looking at the documentation now, I really like the pragmatic approach lol https://github.com/baskerville/bspwm. Source: over 3 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