Exercise 3: Why No Fourth Bootstrap Comparison Was Deliberately Included — Possible Solution ==================================================================== WHAT THE SCOPE NOTE SAYS ------------------------------ Per this chapter's own scope note, this capstone "deliberately doesn't build a fourth Bootstrap-based comparison — cssfw1-5's own material already covered Bootstrap's trade-offs in depth, and adding a fourth full implementation here would dilute this capstone's own focused three-way comparison rather than strengthen it." WHY A FOURTH BOOTSTRAP IMPLEMENTATION WOULD BE REDUNDANT ------------------------------ cssfw1-5 already gave Bootstrap's own real speed advantage, its JavaScript-dependent components, and its genuine customization mechanism (Sass variables) a full, dedicated chapter's worth of honest treatment. Building a fourth, full Bootstrap implementation of the same dropdown component here wouldn't reveal any NEW information about Bootstrap that cssfw1-5 hasn't already covered — Bootstrap's own dropdown component would simply demonstrate the same trade-offs (fast, pre-built, but visually generic unless customized, and JavaScript-dependent) that chapter already established in depth. Repeating that material here as a fourth working example would be duplicative rather than adding genuine new insight. WHY IT WOULD DILUTE THE CAPSTONE'S OWN FOCUSED COMPARISON ------------------------------ Per this chapter's own earlier material, "Why This Comparison Matters" explains that the real point of the three-way comparison is isolating exactly TWO variables — the styling mechanism (Approaches 1 vs. 2) and the behavior/accessibility-ownership mechanism (Approach 2 vs. 3) — so that each transition demonstrates precisely ONE change at a time. Adding a fourth, fully pre-built Bootstrap implementation would introduce a THIRD kind of variable (a complete, pre-designed, bundled- behavior component) that doesn't fit cleanly into that same clean, two-variable comparison structure — it would make the overall comparison harder to follow, not easier, since Bootstrap's own trade- offs aren't really commensurable with the specific "same behavior code, different styling" vs. "same styling, different behavior ownership" axes the other three approaches were deliberately built to isolate. WHY THIS IS A DELIBERATE SCOPING DECISION, NOT AN OVERSIGHT ------------------------------ The chapter explicitly names this exclusion and explains the reasoning behind it directly in its own scope note, rather than silently omitting Bootstrap without comment. This is the same pattern this course has used throughout — explicit, stated scope decisions (per, for example, sqlite1-10's and postgres1-12's own capstone precedents) rather than gaps left unacknowledged. Naming the exclusion and its reasoning explicitly is itself evidence that it was a deliberate choice made in service of a clearer, more focused final comparison, not something simply forgotten. WHY THIS WORKS AS AN ANSWER ------------------------------ It explains specifically why a fourth Bootstrap implementation would be redundant (cssfw1-5 already covered its trade-offs) and would dilute the capstone's own carefully isolated two-variable comparison structure, and identifies the chapter's own explicit acknowledgment of the exclusion as evidence it was a deliberate choice.