Every Lisp needs its own machine.
This one belongs to the OLPC XO-1.
So far, it features:
* Integer & Real numeric types
* Mark & Sweep garbage collection
* A simple foreign function interface
* A full screen editor which can freely mix text and graphics
* Implemented in ~2000 lines of C code
* Released under a MIT/X11 license
UPDATE: Thank you to a friend who shall remain nameless for pointing out that one should probably mention such things… I am currently available for interesting short-term offsite work. 
Highly recommended:
svn co http://v8.googlecode.com/svn/trunk
Cum dubia et fragilis sit nobis vita tributa, in morte alterius spem to tibi ponere noli.
– cato
ignorance -> fear -> hate -> violence -> shame -> war
information -> relief -> embarrassment -> humor -> friendship -> peace
The Workshop on Self-sustaining Systems (S3) is a forum for discussion of topics relating to computer systems and languages that are able to bootstrap, implement, modify, and maintain themselves. One property of these systems is that their implementation is based on small but powerful abstractions; examples include (amongst others) Squeak/Smalltalk, COLA, Klein/Self, PyPy/Python, Rubinius/Ruby, and Lisp. Such systems are the engines of their own replacement, giving researchers and developers great power to experiment with, and explore future directions from within, their own small language kernels. S3 took place May 15-16, 2008 at the Hasso-Plattner-Institute in Potsdam, Germany.
Videos of the talks are being posted at:
.
.
.
weep
.
.
.
I knew a man who lived in fear
it was huge it was angry
it was drawing near
Behind his house a secret place
was the shadow of the demon
he could never face.
He built a wall of steel and flame
and men with guns to keep it tame
Then standing back he made it plain
that the nightmare would never ever rise again
But the fear and the fire and the guns remain.
It doesn’t matter now it’s over anyhow
He tells the world that it’s sleeping
But as the night came round I heard
it slowly sound
it wasn’t roaring it was weeping
it wasn’t roaring it was weeping.
SAX
And then one day the neighbours came
they were curious to know about the smoke and flame
They stood around outside the wall
but of course there was nothing to be heard at all
“My friends”, he said, “we’ve reached our goal
the threat is under firm control
As long as peace and order reign
I’ll be damned if I can see a reason to explain
Why the fear and the fire and the guns remain”.
It doesn’t matter now it’s over anyhow
He tells the world that it’s sleeping
But as the night came round I heard
it slowly sound
it wasn’t roaring it was weeping
it wasn’t roaring it was weeping.
SAX
It doesn’t matter now it’s over anyhow
He tells the world that it’s sleeping
But as the night came round I heard
it slowly sound
it wasn’t roaring it was weeping
it wasn’t roaring it was weeping.
Composed by: Heymann/ Fox/ Cohen/ Cohen
Recorded and released by Bright Blue in 1987.
Legend:
[] = task
. = task length / buffer
w = working
f = finished
Project# 1
-- time -->
Estimate:
[.........][.....][......][.......]
Actual:
[wwwwwf...][wwwwwwwwww][wf....][wwwwwww]
Four tasks.
One task is late.
One task is on time.
Two tasks are early.
But still, we are late:
Management Policies:
Project# 2
-- time -->
Estimate:
[.........][.....][......][.......]
Normalize:
[][][][][.........................]
Actual:
[wwwwwf][wwwwwwwwww][wf][wwwwwww]
Same four tasks. Same task performance.
But now we’re early.
Management Policies:
Project#1 is a machine which can only ever accumulate the negative effects of inaccuracies in estimations.
Project#2 is a machine which can take advantage of the fact that inaccuracies go BOTH ways. Some finish later than others but some also finish _earlier_ than others.
It gets more complex in practice, but this is the fundamental principle.
(Thanks for bringing this up Mike !)
