What the utter fuck are you talking about? How is synchronous vs asynchronous in any way relevant to the conversation? The only reason anything web based was synchronous was incidental to bandwidth being 14.4k baud modems and server processing not able to keep up with the power of the average cel phone we carry in our pockets today. Actually, I haven't checked, but I bet the avarage raspberry pi kit you can buy today had more processing power than anything that could have been called a server in 1990/2 era or whatever. To the extent that ANYTHING was designed with synchronous transactions in mind was incidental that any coder working on any of this stuff in the early 90s was a young adult in the 80s, most of whom had no access to any nice machinery because it was just that rare, and couldn't even BEGIN to imagine any of the ways the technology would be used. If anything, we should be bitching and complaining about why full async support did not appear until 1999 when Lisp machines, unix, multics and everything from Lisp through APL through Prolog supported all the concepts necessary to implement a fully async networked world even back then. It all technically existed and was working in places like Xerox Parc, various university research departments and even started to be deployed in corps that could afford a fully networked async world. Fuck, Lotus Notes was built in the 80s for the CIA (or NSA? can't remember) and had FULL SYNCHRONOUS AND ASYNCHRONOUS replication capability from the start, all the encription, user management, database (okay hierarchical databases but whatever) already built. All that would have needed to happen would be to open source the technology, reduce it to a set of protocols and use the Notes/Domino framework as a reference implementation that others could use to implement their own ecosystems and we would have had fully synchronous behaviour from the very beginning. The web sucks because humans ... actually I don't know why it sucks. I'm not even sure that it sucks.