{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"No Compromises","title":"Blade includes vs components: how we decide","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/e1200f77\"></iframe>","width":"100%","height":180,"duration":955,"description":"Blade gives you two big levers for keeping views maintainable: @include and Blade components.\nWhen should you use one versus the other?\nDoes it matter?\nIn 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).\nWe also touch on scope pitfalls, “passing for documentation,” and why performance worries usually lie elsewhere.\nSign up for the free Mastering Laravel newsletter. The highest value-to-time ratio you will find.","thumbnail_url":"https://img.transistorcdn.com/Z2EtRaIjEnyUZU7bc944H_cjygcmUk4l_35aeIjws5o/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzIzMDM3LzE2Mjc1/MjExMTAtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}