Okay fine not necessarily state, but *some* controlled transient persistence model that’s decoupled from browser session but is less expensive/permanent than on-chain, while still being Web3 native paradigm-wise.
Replying to
Quote Tweet
State is usually bad. What you really want in most situations are values and references (see infoq.com/presentations/ and infoq.com/presentations/).
Show this thread
3
17






