When plain code suffices.
WHAT THE PLATFORM PROVIDES NOW
Module loading Element selection and manipulation Fetching data Custom elements Templating, adequately Animation Storage
WHAT THAT MEANS
Much of what required a library ten years ago no longer does.
WHAT SUITS PLAIN CODE
Content sites with some interactivity Forms with enhanced validation Widgets on otherwise static pages Anything small
WHAT IT AVOIDS
A build step A runtime shipped to visitors Dependency maintenance Framework version migrations
WHAT IT COSTS
Writing structure and conventions yourself More discipline required
WHAT TO ADOPT IF WORKING THIS WAY
A module structure A naming convention A small set of utilities, written once
WHAT TO CONSIDER FOR MODEST NEEDS
A small library providing reactivity without a build step.
WHAT TO AVOID
Reinventing a framework badly.
WHAT TO RECOGNISE
The point at which the complexity justifies a framework.
