The argument: components shouldn't own their outer spacing

Max Stoiber's position, stated bluntly, is that margin should be banned from components. The claim reads as a blanket attack on a property most developers have used for years without trouble, but that isn't the point being made. A component has no knowledge of the context it will be rendered into, and therefore cannot know what spacing is required around it. The fix he proposes is to hand that responsibility to a parent component.

Where the approach holds up

There is nothing objectionable in that reasoning on its own terms: spacing becomes a property of the layout that arranges children, not of the children themselves. The concern is what component-driven front-ends look like once the pattern is applied broadly. A tree can end up as a route component wrapping a query component wrapping a styled component wrapping a state machine component wrapping a spacer component wrapping some semantic template. That list is long, and many JavaScript-built codebases already nest considerably deeper.

The risk is not componentization as such, but ending up with a structure thick enough that it can no longer be reasoned through. Keeping the tree legible is the constraint that matters when deciding where spacing logic belongs.

The discussion connects to a prediction from Adam Argyle that use of margin will decline entirely, as gap takes over in all-flexbox and all-grid layouts. That shift and Stoiber's parent-owns-the-spacing rule push in the same direction, but from different angles: one is about which property expresses spacing between siblings, the other about which component is entitled to set it.