Make macOS consistently bad (unironically)

A Mac user provides a code-based solution to address the "consistently bad" and aesthetically jarring inconsistent rounded corners in macOS 26. This DIY fix, involving method swizzling and dynamic library injection, appeals to the Hacker News crowd by demonstrating technical prowess in tweaking system UI. The piece sparks a lively debate on Apple's design philosophy, user expectations, and the broader implications of minor UI frustrations on perceived OS quality.

Score

Comments

Highest Rank

26h

on Front Page

First Seen

Mar 27, 7:00 PM

Last Seen

Mar 28, 8:00 PM

Rank Over Time

The Lowdown

The author takes aim at macOS 26 for its perceived UI inconsistency, specifically highlighting the varying and often unattractive rounded corners of windows. They argue that while some find the newer, more extreme roundness ugly, the true problem lies in the lack of uniformity. Rather than fighting roundness, the author proposes a technical solution to make all applications consistently rounded, even if it means embracing a "consistently bad" aesthetic.

The Problem: macOS 26 introduces inconsistent window corner radii, leading to a fragmented user experience where some applications appear modernly rounded while others retain older, sharper designs, or adopt new, less appealing curves (e.g., Safari's "crazy bad corners").
The Solution: A technical patch is provided using Objective-C method swizzling. This code intercepts and overrides the _cornerRadius, _getCachedWindowCornerRadius, _topCornerSize, and _bottomCornerSize methods of NSThemeFrame to force a uniform kDesiredCornerRadius (set to 23.0) for all third-party GUI applications.
Implementation: The fix involves compiling a dynamic library (SafariCornerTweak.dylib), placing it in /usr/local/lib/, signing it, and then configuring a LaunchAgent plist to inject this library into processes using the DYLD_INSERT_LIBRARIES environment variable.
System Integrity Protection (SIP): The author briefly touches on SIP, noting that while disabling it is often suggested for system tweaks, their method primarily targets third-party apps and does not require full SIP disablement, reducing potential security risks (though this point is debated in comments).

Ultimately, this technical workaround offers a way for users to enforce a unified visual style across their macOS environment, prioritizing consistency to mitigate what the author views as Apple's scattered design choices.

The Gossip

Corner Conundrums and Tab Troubles

Many commenters echo the author's frustration with inconsistent UI elements, particularly the varying rounded corners and new "pill-shaped" tabs in macOS Tahoe (presumably macOS 26). Some find the inconsistencies jarring, especially when windows overlap, while others are less bothered or don't even notice. The aesthetic changes are described as both distracting and less informative, leading to debates on subjective design preferences.

Bikeshedding or Breakthrough: The Flaw's True Depth

A significant thread questions whether UI nitpicks like corner radii are truly important. Some argue that if such a minor detail is the biggest complaint, macOS must be a remarkably good OS, dismissing it as "bikeshedding." Counterarguments suggest that these small inconsistencies can signify deeper architectural flaws, a "death by a thousand cuts," or erode user trust in Apple's famed attention to detail, indicating a broader problem with design consistency and user experience.

Window Woes: Maximization and Multitasking

The discussion delves into macOS's window management philosophy, specifically regarding maximizing applications. Many users, both long-time Mac users and those with large monitors, rarely maximize windows, believing macOS is optimized for smaller, tiled arrangements. They criticize the default full-screen behavior (which often creates a new desktop space) as counterproductive to multitasking. This contrasts with Windows users who often expect true maximization, highlighting a fundamental difference in OS interaction paradigms.

SIP Scrutiny: Security vs. System Tweaks

Commenters weigh in on the technical aspects of the solution, particularly the author's claim about System Integrity Protection (SIP). While the author suggests their method circumvents the need for full SIP disablement, some clarify that SIP protects more than just the root directory. The general sentiment is that while tweaking system files carries inherent risks, the impact of disabling SIP for a UI change is debated, with some arguing that if malware already has root, SIP becomes less relevant.