My mental model for UIs is rooted in physical metaphors: steering wheel, speed gauge, light switch, faucets, doors, etc etc and these things don’t make sense as caches in my brain.
it’s maybe the difference between *views* and *controls*
Idk, thanks for the discussion!
My mental model for UIs is rooted in physical metaphors: steering wheel, speed gauge, light switch, faucets, doors, etc etc and these things don’t make sense as caches in my brain.
it’s maybe the difference between *views* and *controls*
Idk, thanks for the discussion!
Point being, a lot of UI just isn’t a cached of data, it’s more like a stream of data.
Point being, a lot of UI just isn’t a cached of data, it’s more like a stream of data.
Obviously this is somewhat trivial but it’s a utility that I personally use regularly that has a good UI and doesn’t strike me as a cache of data. Any sort of “real-time” stream of data fails to fit this mental model of a cache
Obviously this is somewhat trivial but it’s a utility that I personally use regularly that has a good UI and doesn’t strike me as a cache of data. Any sort of “real-time” stream of data fails to fit this mental model of a cache
<p slot=pending>Loading…</p>
<p slot=rejected class=error>
Failed to load.
</p>
<div slot=resolved>
<template id=comment-template>
<p>
<slot name=text></slot>
</p>
</template>
</div>
</use-async>
<p slot=pending>Loading…</p>
<p slot=rejected class=error>
Failed to load.
</p>
<div slot=resolved>
<template id=comment-template>
<p>
<slot name=text></slot>
</p>
</template>
</div>
</use-async>