i think part of the reason why arweave people understand it better is they already have a separation in their architecture between replicas and the consensus and the delivery API service, so it is simpler for them to think of their database as storage, indeed that's one of the whole points of their project is pretty much focused on storage so they have more realistic strategy about how to keep the cost contained and scaling replication to fit the use case instead of having a one-consensus-to-rule-them-all mentality