Libraries for building interfaces.
WHAT THEY PROVIDE
A way of describing interfaces as components Automatic updating when data changes Routing between views Conventions and tooling
WHY THEY EXIST
Managing the document directly becomes unmanageable in complex applications.
WHAT THEY COST
A build step A learning curve Code shipped to every visitor Dependence on an ecosystem
WHEN THEY ARE WARRANTED
Substantial application interfaces Complex state Many interactive views
WHEN THEY ARE NOT
Content sites Pages with modest interactivity Anything a content management system already handles
WHAT THAT MEANS
Many sites built with a framework did not need one.
WHAT TO ASSESS
Whether the complexity justifies it.
WHAT TO CHOOSE ON
Whether it fits the problem How widely used it is How well documented Whether your team knows it
WHAT NOT TO CHOOSE ON
Novelty.
WHAT TO CONSIDER
That frameworks change, and applications built on them require ongoing maintenance.
