Status: IN
The State pattern provides a distinct behavioral modeling mechanism: it differs from Strategy in binding transitions to object state rather than client-selected algorithms, and from table-driven approaches in representing state-specific behavior as polymorphic objects rather than lookup entries — with object creation tradeoffs (eager singletons vs. lazy on-demand) reflecting deployment context.
State occupies a unique niche defined by contrast with Strategy (different binding) and tables (different representation), plus its own creation tradeoffs
Depends on (SL): strategy-vs-state-distinction, gof-state-vs-table-driven-key-difference, gof-state-object-creation-tradeoff