slightlyoff@toot.cafe ("Alex Russell") wrote:
Basically, you want to divide your cumulative costs by the number of trips through the interaction loop per session.
A theoretical case for this technology that falls out of a tiny model like this, and apologists for client-side bloat (which, at this point, seems to be most of the frontend world?) could be putting forward metrics with interaction depth amortization too...but they haven't.