Posts tagged computation

Distributed Autonomous Corporations (DACs) are a generalization of the concept of a crypto-currency where the currency is backed by the services its miners perform rather than a real-world commodity like gold, oil, or, ahem, thin air. If we can barter for goods and services, why can’t we back currencies with goods or services? DACs may be simultaneously viewed as crypto-currencies and unmanned businesses. As businesses, they perform services intended to be valuable to their customers. Such services might include money transmission (Bitcoin), asset trading (BitShares), domain name services (DomainShares), or a thousand other business models sure to emerge as people realize that DACs are not mere “altcoins”.

http://invictus-innovations.com/i-dac/

Computing is a high-level process of a physical system. Recent interest in non-standard computing systems, including quantum and biological computers, has brought this physical basis of computing to the forefront. There has been, however, no consensus on how to tell if a given physical system is acting as a computer or not; leading to confusion over novel computational devices, and even claims that every physical event is a computation. In this paper we introduce a formal framework that can be used to determine whether or not a physical system is performing a computation. We demonstrate how the abstract computational level interacts with the physical device level, drawing the comparison with the use of mathematical models to represent physical objects in experimental science. This powerful formulation allows a precise description of the similarities between experiments, computation, simulation, and technology.

http://arxiv.org/abs/1309.7979

Behind every value lies a computation struggling to get out. That’s the idea behind what I call the explodable user interface. (Forget wearable. Explodable.) By “explodable” what I have in mind is the ability to pick any part of an application’s GUI that you happen to be interested in and interactively “unpack” it into a story that explains how it was computed. It should be as though code lurks behind everything you can see, all the way back to the data sources your application works with. In Lisp you can explode an atom into its constituent characters, but the relationship between a Lisp atom and its characters has no computational content to speak of. In a typical application, the relationship between a value and its parts is non-trivial. If it were otherwise, you wouldn’t call it an “application”: you’d call it “a bunch of data”. Whenever this non-trivial structure is present, you should be able to browse into it in order to understand it or change it.

http://dynamicaspects.org/blog/2012/06/10/self-explaining-computation–2/