Episode
Blade includes vs components: how we decide
- Podcast
- No Compromises
- Published
- Aug 16, 2025
- Duration seconds
- 955
- Processing state
not_requested- Canonical source
- https://share.transistor.fm/s/e1200f77
Actions
POST https://stenobird.com/v1/public/podcasts/no-compromises-1309932/episodes/blade-includes-vs-components-how-we-decide/transcription-requests
Idempotently request low-priority transcript generation for this episode.GET https://stenobird.com/podcast/no-compromises-1309932/blade-includes-vs-components-how-we-decide.md
Read the agent-friendly Markdown representation of this episode resource.
Summary
Blade gives you two big levers for keeping views maintainable: @include and Blade components. When should you use one versus the other? Does it matter? In the latest episode of the No Compromises podcast, we lay out a clear heuristic for when to extract markup for organization (includes) versus when to encapsulate and reuse with controlled scope (components). We also touch on scope pitfalls, “passing for documentation,” and why performance worries usually lie elsewhere. Sign up for the free Mastering Laravel newsletter . The highest value-to-time ratio you will find.