Activity Monitor on macOS reveals a staggering number of processes, often exceeding 700 even with no applications running. Many of these are essential, but there’s a persistent interest in determining which could be eliminated to streamline performance. Identifying unnecessary processes is complicated by the interconnected nature of macOS components. The author points out that studying 500 processes, each requiring about a week of research, would take over 10 years, making it impractical given the constant updates and changes. Focusing on processes related to Time Machine, which many users don’t utilize, the article highlights how these backup processes persist even when Time Machine is disabled. For instance, processes like `backupd` and `backupd-helper` continue to consume CPU and memory. These processes are managed by LaunchDaemons located in the Signed System Volume, which prevents users from directly modifying them. The scheduling of Time Machine backups has evolved, relying on systems like the Duet Activity Scheduler (DAS) and Centralized Task Scheduling (CTS). Even without Time Machine enabled, these systems continue to schedule backup tasks, which may seem wasteful but occur with minimal resource impact. The author contrasts modern macOS with earlier versions, noting the reduced modularity and choice for users. Unlike Mac OS 9, where users could pick and choose components, modern macOS limits user control over running processes due to its design and architecture. Features like the Signed System Volume and the new scheduling frameworks restrict the ability to remove or disable processes, underscoring a shift toward a more controlled operating environment.