Life & Research Notes

Programming methodology typically focuses on abstraction of complexity. A decent programmer attempts to reuse code and standards and protocols that already exist, and writes code that is well documented and easily reused by others for purposes not necessarily originally intended.

This trend towards abstraction affects the sorts of programming languages that we use. Originally people wrote their code in binary, then assembly, then later something like FORTRAN or C (or alternatively Lisp), then C++, Java, and now Ruby or Python (and many others). Each language offers greater abstraction over the previous generation, hiding some of the underlying complexity and offering more builtin capabilities and greater extensibility.

With web and net oriented programming we are beginning to see the abstraction of the complexity over human distance. Similar to how I can check my gmail from anywhere in the world, I can also write a program that uses a web service protocol like XML-RPC or SOAP to use code and processing resources made available by other providers. Web services are one of the primary technologies in OPENSTUDIO, and are one of the key building blocks of this latest Web 2.0 boom.

I believe the next step, the Web 3.0 step, is abstraction of duration. In a previous post I referred to this approach as Slow Computing. Obviously being slow means that it has something to do with time. Originally I was going to title this post Slow Computing is the Abstraction of Time, but Burak convinced me that what I really intend here is duration: the time between two events. Programming for Slow Computing will involve making use of libraries and objects and methodologies that abstract duration, allowing programs to run over days and years, waiting for and responding to events that unfold at a human pace.

Relevant links pointed out to my today by visiting friend Ty:

• The Long Now Foundation
• Long Bets

respond / trackback