KIV : front-end web framework concerns

 Momentary recap of things I want in a front-end web framework :

• - no DSLs : no TypeScript, no templating language, no weird custom attributes ( is it possible to just use [data-*] ? )
• - no build-step : any compilation / transpilation / code generation defaults to runtime, unless otherwise flagged for optimisation
• - hew closely to REST : servers should not memorise client state; but it should be possible for clients and servers to switch roles ( both are fundamentally hosts ); browsers can have rather long-term persistent storage, standardised circa 2014
• - hew closely to webComponents standard

Not sure yet : 

• - to vDOM or not to vDOM
• - swappable protocols for render batching
• - swappable protocols for application state management
• - render optimisations with 
• intersectionObserver, 
• getBoundingClientRect, 
• CSS containment, 
• img[loading=lazy], 
• link[media] unblocking, 
• unifying scroll-windowing with pagination, 
• textarea[various=off]