saved articles

Core Features PIP is a messaging standard that is -Locally Stateful -Asynchronous -ZK-STARK Encrypted -Meshnet based This allows for peer-to-peer interactions that are computed fully clientside Why Clientside? The advent of Cloud Computing has created a flourishing of feature rich web applications whose loads are serverheavy. This has caused a series of unwanted side effects as data privacy, siloed data, and routing inefficiency cause a suboptimal user experience. Prioritising state synchronisation and distributed computing through the use of blockchain consensus has created a fundamental paradigm WRT what is possible with Cloud. The Opportunity Thanks to recent developments, several conceptual trends that favour clientside are now possible for the first time: Blockchain Rollups allow for server synchronisation with relatively small computational loads Modern browser telecommunications infrastructure can run such loads with sufficient throughput and liveness guarantees for consumer...

Abstract Lisp has done quite well over the last ten years: becoming nearly standardized, forming the basis of a commercial sector, achieving excellent performance, having good environments, able to deliver applications. Yet the Lisp community has failed to do as well as it could have. In this paper I look at the successes, the failures, and what to do next. The Lisp world is in great shape: Ten years ago there was no standard Lisp; the most standard Lisp was InterLisp, which ran on PDP-10s and Xerox Lisp machines (some said it ran on Vaxes, but I think they exaggerated); the second most standard Lisp was MacLisp, which ran only on PDP-10s, but under the three most popular operating systems for that machine; the third most standard Lisp was Portable Standard Lisp, which ran on many machines, but very few people wanted to use it; the fourth most standard Lisp was Zetalisp, which ran on two varieties of Lisp machine; and the fifth most standard Lisp was Scheme, which ran on a few differe...