waydabber/BetterDisplay
Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.
waydabber/BetterDisplay
BetterDisplay is an active, highly starred macOS display utility focused on advanced monitor control and scaling. It appears fork-friendly mainly for people interested in display-management features, macOS compatibility work, or release/documentation-driven changes rather than a large codebase, since the repository snapshot shows only a top-level README and no detected source directories.
Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.
Choose a fork to inspect
Prefer upstream unless you specifically need this unchanged snapshot. This fork has no visible added capabilities, is 58 commits behind, and looks stale rather than maintained.
Prefer this fork if your only goal is dummy-display-based HiDPI scaling and you want a smaller, more focused tool. Prefer upstream BetterDisplay if you need the broader brightness, HDR, DDC, virtual-screen, EDID, and synchronization features, or if you care more about ongoing maintenance.
Choose this fork only if the dummy-display/HiDPI use case is the whole requirement. If you need active maintenance or BetterDisplay's broader monitor-control features, upstream is the safer choice.
Choose this fork only if you specifically want the dummy-display use case. For anyone who wants the broader BetterDisplay feature set or current macOS compatibility work, upstream is the better default.
Choose this fork if you specifically want a focused dummy-display/HiDPI tool and do not need BetterDisplay’s newer advanced display features. Avoid it if you want an actively maintained, broad-spectrum display utility or expect current macOS compatibility work.
Choose this fork if your only goal is dummy-display-driven custom HiDPI resolution support. Choose upstream if you want the broader, actively updated BetterDisplay feature set or better odds of current macOS compatibility.
Prefer upstream unless you explicitly need this older snapshot; this fork adds no visible value and is behind active development.
Adopt this fork only if you specifically want the upstream code state as of the fork point; otherwise upstream is the better choice because this fork adds nothing and is 59 commits behind.
Prefer upstream unless you specifically need this older snapshot; this fork offers no visible enhancements and is materially behind current upstream development.