Exercise 1: Why macOS Has No Built-In Package Manager — Possible Solution
====================================================================

WHY MACOS HAS NO EQUIVALENT TO APT/DNF/PACMAN/APK
------------------------------
Per this chapter, every Linux distribution ships an official, OS-vendor-maintained package manager as a core part of the operating system itself, because installing and updating software has always been treated as part of the OS vendor's own responsibility on Linux. Apple never built an equivalent, general-purpose command-line/developer-tooling package manager into macOS - its own distribution model instead centers on the Mac App Store and direct .dmg/.pkg downloads for GUI software, leaving open-source command-line tooling as something Apple simply never took on as its own problem to solve.

WHAT ACTUALLY FILLS THE GAP
------------------------------
Homebrew - an unofficial, community-built, open-source project created in 2009 by Max Howell - fills the gap, entirely independent of Apple.

WHY THE MAC APP STORE DOESN'T COUNT
------------------------------
The chapter is explicit that the Mac App Store is a fundamentally different category of thing: a curated, sandboxed storefront specifically for consumer GUI applications, reviewed and approved by Apple. It has no mechanism for installing command-line tools, developer libraries, or the kind of open-source software a general package manager like apt or pacman handles - so even though it's a real, built-in way to install some software, it doesn't fill the same role a general package manager fills on Linux.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly explains that macOS's absence of a built-in package manager stems from Apple's own GUI-centric distribution model rather than an oversight, correctly names Homebrew as the actual gap-filler, and explains specifically why the Mac App Store's curated, GUI-only, sandboxed scope disqualifies it from counting as an equivalent.