Web3 is a stupid idea
Really wish progressive enhancement was chosen as the first thing, want to get rid of the backend db? ok, two APIs,<p>store to extension-managed DB (e.g. flatfiles in the home directory, or shunted onto something managed with LDAP, or loaded onto some weird coin thing on a local light node, or etc),<p>or in environments where extensions are fussy &#x2F; overcomplicated, store to another website via a http api (la <a href="https:&#x2F;&#x2F;remotestorage.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;remotestorage.io&#x2F;</a>, or if one wants to overcomplicate it again, a remotestorage-to-weird-blockchain-thing-shim)<p>- - -<p>For the article itself, deriding web3 as &quot;Money websites&quot; and then basically asking for &quot;Lightweight money websites&quot; is a bit pointless. Storing stuff on &quot;Money&quot; is a big overhead, If you were to decide to write your data onto a gold ingot, you&#x27;d probably not enjoy the process of going to the bank safe deposit box each time to make a change or read a change, likewise, money websites are going to be encumbered with risk, endless layers of crypto math un-understanding, and stress.<p>Don&#x27;t worry, someone might make a contract to provide that fine grained API you want, and that contract might not have bugs, and the tooling used might not be able to be tricked to use some other contract as an api since you know, decentralized, shouldn&#x27;t be able to use only 1 implementation right<p>Or, if you remove money from the equation, like, hell, replace it with text files or something, even if users need to exchange text files with each other to update each other&#x27;s pages (ok a bit overkill, webrtc should suffice, still requires both people online at the same time though), it still removes a lot of emotional stress