Exercise 1: The Genuine Capability Difference — Possible Solution
====================================================================

WHAT WAS STRUCTURALLY IMPOSSIBLE IN DTL
------------------------------
Per this chapter (and Django Rebuild 4 before it), Django's DTL deliberately has no arbitrary function calls, real expressions, or general-purpose logic - there is no way to write a genuine, open-ended loop that walks upward through an unknown number of parent relationships directly inside a DTL template. This is exactly why Django's own breadcrumb-building code had to live in the view (Python), with the template only ever iterating an already-completed, flat list handed to it.

WHAT IS ACTUALLY POSSIBLE IN BLADE
------------------------------
Per this chapter, Blade's @php/@endphp block contains real, genuinely executable PHP - the exact same while loop that walks $page->parent repeatedly, building the breadcrumb array, can be written directly inside a Blade template and it actually runs correctly, producing the same breadcrumb Django's Controller-equivalent code produces. This isn't a workaround or a hack - it's a real, intentional, documented Blade feature.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly explains that DTL structurally cannot express the arbitrary-depth walk required for a breadcrumb, and correctly explains that Blade's @php block genuinely can execute that same logic directly inside the template, illustrating a real, not merely cosmetic, capability difference between the two templating languages.