Declarative Programming

The author Steven Pemberton, CWI, Amsterdam

Contents

1957: The first municipal computer (Norwich, UK)

The First Computer in Norwich

Just one of 21 cabinets making up the computer.

2015: The Raspberry Pi Zero

Raspberry Pi in Norwich

The first computer so cheap that they gave it away on the cover of a magazine

How do they compare?

The Elliot ran for about a decade, 24 hours a day.

How long do you think it would take the Raspberry Pi Zero to duplicate that amount of computing?

How do they compare?

The Elliot ran for about a decade, 24 hours a day.

How long do you think it would take the Raspberry Pi Zero to duplicate that amount of computing?

The Raspberry Pi is about one million times faster...

Compare

The Raspberry Pi is not only one million times faster. It is also one millionth the price.

A factor of a million million.

A terabyte is a million million bytes: nowadays we talk in terms of very large numbers.

Want to guess how long a million million seconds is?

Compare

The Raspberry Pi is not only one million times faster. It is also one millionth the price.

A factor of a million million.

A terabyte is a million million bytes: nowadays we talk in terms of very large numbers.

Want to guess how long a million million seconds is?

30,000 years...

A really big number...

Moore's Law

In fact a million million times improvement is about what you would expect from Moore's Law over 58 years.

Except: the Raspberry Pi is two million times smaller as well, so it is much better than even that.

This probably has to do with how early computers were priced.

How computers were priced

Pre computers computing

When Edison introduced electric light in the home, he charged not what it cost to produce the electricity, but what it would cost you to produce the same light without electricity, but now with extra advantages, such as instant-on, and less danger.

Similarly, the first computers were not priced on how much they cost to produce, but on how much you would have to pay to do the same work without computers.

Moore's Law: not dead yet

42 years of processors

An article by a journalist who had been mourning Moore's Law for a decade, and realised he was wrong.

1957

In the 50's, computers were so expensive that nearly no one bought them, nearly everyone leased them.

To rent time on a computer then would cost you of the order of $1000 per hour: several times the annual salary of a programmer!

When you leased a computer in those days, you would get programmers for free to go with it.

Compared to the cost of a computer, a programmer was almost free.

The design of programming languages

The first programming languages were designed in the 50s:

Cobol, Fortran, Lisp, Algol.

They were designed with that economic relationship of computer and programmer in mind.

It was much cheaper to let the programmer spend lots of time producing a program than to let the computer do some of the work for you.

Programming languages were designed so that you tell the computer exactly what to do, in its terms, not what you want to achieve in yours.

Back to now

It happened slowly, almost unnoticed, but nowadays we have the exact opposite position:

Compared to the cost of a programmer, a computer is almost free.

I call this Moore's Switch.

Moore's Switch

Moore's Switch illustrated
Relative costs of computers and programmers, 1957-now

But, most programmers are still using languages that are direct descendants of the languages designed in the 1950's!

We are still telling the computers what to do.

Declarative programming

A new way of programming: describes what you want to achieve, but not how to achieve it..

Let me give some examples

The first declarative definition

Declarative approaches describe the solution space.

A classic example is when you learn in school that

The square root of a number n is the number r such that r × r = n

This doesn't tell you how to calculate the square root; but no problem, because we have machines to do that for us.

Procedural code

function f a: {
    x ← a
    x' ← (a + 1) ÷ 2
    epsilon ← 1.19209290e-07
    while abs(x − x') > epsilon × x: {
        x ← x'
        x' ← ((a ÷ x') + x') ÷ 2
    }
    return x'
}

This is why documentation is so essential in procedural programming.

What does 'Declarative programming' mean?

A Procedural Clock

A clock in C, 1000+ lines

1000 lines, almost all of it administrative. Only 2 or 3 lines have anything to do with time.

And this was the smallest example I could find. The largest was more than 4000 lines.

A Declarative Clock

type clock = (h, m, s)
displayed as 
   circled(combined(hhand; mhand; shand; decor))
   shand = line(slength) rotated (s × 6)
   mhand = line(mlength) rotated (m × 6)
   hhand = line(hlength) rotated (h × 30 + m ÷ 2)
   decor = ...
   slength = ...
   ...
clock c
c.s = system:seconds mod 60
c.m = (system:seconds div 60) mod 60
c.h = (system:seconds div 3600) mod 24

A Running Declarative Clock

The Views System

XForms

XForms is a declarative system for defining applications. BBC Sport App

It is a W3C standard, implementations from NL, FR, BE, UK, DE, US, and in worldwide use.

Example: 150 person years becomes 10!

A certain company makes one-off BIG machines (walk in): user interface is very demanding — traditionally needed:

5 years, 30 people.

With XForms this became:

1 year, 10 people.

Do the sums. Assume one person costs 100k a year. Then this has gone from a 15M cost to a 1M cost. They have saved 14 million! (And 4 years)

Example: Insurance Industry

Manager: I want you to come back to me in 2 days with estimates of how long it will take your teams to make the application.

Example: Insurance Industry

Manager: I want you to come back to me in 2 days with estimates of how long it will take your teams to make the application.

[Two days later]

Programmer: I'll need 30 days to work out how long it will take to program it.

Example: Insurance Industry

Manager: I want you to come back to me in 2 days with estimates of how long it will take your teams to make the application.

[Two days later]

Programmer: I'll need 30 days to work out how long it will take to program it.

XFormser: I've already programmed it!

Example: NHS

The British National Health Service started a project for a health records system.

Example: NHS

The British National Health Service started a project for a health records system.

One person then created a system using XForms.

XForms

XForms 1.0 was designed for online Forms.

After some experience it was realised that the design had followed HTML too slavishly, and with some slight generalisation, it could be more useful.

So was born XForms 1.1, a Turing-complete declarative programming language.

Implementations from Belgium, France, Germany, NL, UK, USA.

XForms 2.0 is in preparation.

Form and content

Wikipedia:

"The term form refers to the work's style, techniques and media used, and how the elements of design are implemented.

Content, on the other hand, refers to a work's essence, or what is being depicted."

This is a nearly-perfect description of XForms.

XForms applications have two parts:

  1. the model, describing the data, and its relationships;
  2. the user interface, describing the content, and connecting to the values in the model.

State

XForms is all about state. (Which means it meshes well with REST - Representational State Transfer).

Initially the system is in a state of stasis.

When a value changes, by whatever means, the system updates related values to bring it back to stasis.

This is like spreadsheets, but much more general.

The result is: programming is much easier, since the system does all the administrative work for you.

Example

I've got a position in the world as x and y coordinates, and I want to display the map tile of that location at a certain zoom.

My data:

x, y, zoom

Openstreetmap has a REST interface for getting such a thing:

http://openstreetmap.org/<zoom>/<x>/<y>.png

Map interface

However, the Openstreetmap coordinate system changes at each level of zoom.

As you zoom out, there are in each axis half as many tiles, so there are ¼ as many tiles. And the interface indexes tiles, not locations.

So to get a tile:

  1. You have to know how big a tile is
  2. you have to calculate the correct index using this plus the zoom.

Declarative Example

The data: x, y, zoom

scale = 226 - zoom
tilex = floor(x/scale)
tiley = floor(y/scale)
url = concat("http://tile.openstreetmap.org/", zoom, "/", tilex, "/", tiley, ".png")

That is really all that is needed (modulo syntax, which looks like this:)

<bind ref="tilex" calculate="floor(../x div ../scale)"/>

That's the form. Now the content:

<input ref="zoom" label="zoom"/>
<input ref="x" label="x"/>
<input ref="y" label="y"/>
<output ref="url" mediatype="image/*"/>

and the tile will be updated each time any of the values change.

Live tile with zoom

Source

Map

Source

Map

Source

XForms, an overview

Separation of data from UI, similar to separation of style from content with CSS, with similar advantages.

Instances of data + properties.

<instance src="data.xml"/>
<bind ref="something" property="something"/>

Properties include:

As you saw above in the map example, whenever a value changes, the related values are automatically updated, in spread-sheet style.

Example properties: relevant and required

<bind ref="address/state"
      required="../country = 'USA'"/>

This means that state is only required for the USA. The field will always be visible.

<bind ref="address/state"
      relevant="../country = 'USA'"
      required="true()"/>

This means that state will only be visible for the USA, but once visible will be required.

Controls in the UI then bind to data nodes, inheriting their properties.

<input ref="address/state" label="State"/>

Relevance

Here is an example. If you select USA as country, the control for state appears.

Source

Relevance

Similarly, the billing address is only relevant if it is different from the delivery address:

<bind ref="address[@type='Billing']"
      relevant="../@different=true()"/>

Relevance

Source

Events and Actions

Typically XForms works automatically.

But you can hook into the processing model to respond in special ways.

Events announce changes in the state;
actions
effect changes to the state.

E.g. xforms-ready announces that the system has initialised (and is at stasis). You could respond to this by recording today's date and time:

<action ev:event="xforms-ready">
   <setvalue ref="today" value="now()"/>
</action>

Events and Actions

Other events announce when a value changes, or when it changes validity, relevance, etc.

Other useful actions include setting a value, and inserting and deleting elements and attributes from data.

In fact the only way to get a vanilla button to do anything is to listen for the activation event, and then respond with an action.

<trigger label="Restart">
   <action ev:event="DOMActivate">
      <setvalue ref="score" value="0"/>
   </action>
</trigger>

Content

The user-facing part is done with controls.

Controls are declarative too: they are designed to be device and modality independent, and describe what they do, but now how they do it, nor how they look.

Example control

For instance, the select1 control selects a value from a list of values. It can be implemented visually as a menu, or as radio buttons, and it can be implemented in other modalities as necessary.

<select1 ref="colour">
   <label>Colour:</label>
   <item><label>Red</label><value>red</value></item>
   <item><label>Yellow</label><value>yellow</value></item>
   <item><label>Green</label><value>lime</value></item>
   <item><label>Cyan</label><value>aqua</value></item>
   <item><label>Blue</label><value>blue</value></item>
   <item><label>Magenta</label><value>fuchsia</value></item>
   <item><label>Black</label><value>black</value></item>
   <item><label>White</label><value>white</value></item>
</select1>

For instance these three are just different visual representations of this control:

Source

Controls adapt

Controls can adapt to the type of value they are bound to.

<input ref="x"/>

Source

Dynamic Controls

Controls can also get their labels and content from data.

<select1 ref="colour">
   <label ref="messages/colour"/>
   <itemset ref="colours/colour">
      <label ref="."/>
      <value ref="@code"/>
   </itemset>
</select1>

using data like

<instance>
   <data xmlns="">
      <colours>
         <colour code="red">red</colour>
         <colour code="yellow">yellow</colour>
         <colour code="lime">green</colour>
         ...
      </colours>
      <messages>
         ...
         <colour>Colour:</colour>
         ...
      </messages>
   </data>
</instance>

Multilingual

Here it is in use:

Source

Conclusion

For historical reasons, present programming languages are at the wrong level of abstraction: they don't describe the problem, but only one particular solution.

Declarative programming allows programmers to be ten times more productive: what you now write in a week, would take a morning; what now takes a month would take a couple of days.

Once project managers realise they can save 90% on programming costs, they will switch to declarative programming.

I believe that eventually everyone will program declaratively: fewer errors, more time, more productivity.

XForms is work in progress; version 2 is in preparation.

Clock

Source