Skip to main content

Let's raise £500k for the Analytical Engine

If you are new to this please read my introduction to Babbage's 100-year Leap. If not, read on...



I've created a PledgeBank entry for the project here where I'm asking people to pledge to donate $10/£10/€10 towards a non-profit organization dedicated to building the Analytical Engine. The non-profit would have four goals:

1. To help digitize and make available in electronic form all of Charles Babbage's notes and plans associated with the Difference Engine and Analytical Engine.

2. To fund the study of Babbage's Analytical Engine plans to determine what best constitutes a complete design for the Engine.

3. To coordinate the building of a computer simulation of the Analytical Engine that shows its working in 3D with accurate physics.

4. To build the Analytical Engine and donate it to a museum in Great Britain for public display.

PledgeBank operates on an all-or-nothing system where I either reach the goal and then can ask people to make good on their pledge, or I fail. Please consider signing up to pledge $10/£10/€10 towards these goals.


Sign my pledge at PledgeBank

Comments

Ruben Berenguel said…
I don't have my credit card here, but later as I get back home I'll sign up. It would be an awesome endeavour John.

Cheers,

Ruben
Latest in my blog: And e/2 Appears from Nowhere
You don't need a credit card. Just sign the pledge, you don't need to hand over any money right now.
Simon Zerafa said…
Hi,

I have added my name to the plege and will tweet the details later.

Lets hope we can get more folks onboard and get this project off the ground!

Kind Regards

Simon Zerafa
Ruben Berenguel said…
I wasn't aware of that, done!
Unknown said…
http://www.facebook.com/group.php?gid=147096618666449

Facebook group up. invite your friends!
Unknown said…
Just got an email from PledgeBank saying it's game over. I don't care--where can I donate? ;-)
Unknown said…
Just sending a comment now signed in to subscribe to replies.

Popular posts from this blog

How to write a successful blog post

First, a quick clarification of 'successful'. In this instance, I mean a blog post that receives a large number of page views. For my, little blog the most successful post ever got almost 57,000 page views. Not a lot by some other standards, but I was pretty happy about it. Looking at the top 10 blog posts (by page views) on my site, I've tried to distill some wisdom about what made them successful. Your blog posting mileage may vary. 1. Avoid using the passive voice The Microsoft Word grammar checker has probably been telling you this for years, but the passive voice excludes the people involved in your blog post. And that includes you, the author, and the reader. By using personal pronouns like I, you and we, you will include the reader in your blog post. When I first started this blog I avoid using "I" because I thought I was being narcissistic. But we all like to read about other people, people help anchor a story in reality. Without people your bl

Your last name contains invalid characters

My last name is "Graham-Cumming". But here's a typical form response when I enter it: Does the web site have any idea how rude it is to claim that my last name contains invalid characters? Clearly not. What they actually meant is: our web site will not accept that hyphen in your last name. But do they say that? No, of course not. They decide to shove in my face the claim that there's something wrong with my name. There's nothing wrong with my name, just as there's nothing wrong with someone whose first name is Jean-Marie, or someone whose last name is O'Reilly. What is wrong is that way this is being handled. If the system can't cope with non-letters and spaces it needs to say that. How about the following error message: Our system is unable to process last names that contain non-letters, please replace them with spaces. Don't blame me for having a last name that your system doesn't like, whose fault is that? Saying "Your

The Elevator Button Problem

User interface design is hard. It's hard because people perceive apparently simple things very differently. For example, take a look at this interface to an elevator: From flickr Now imagine the following situation. You are on the third floor of this building and you wish to go to the tenth. The elevator is on the fifth floor and there's an indicator that tells you where it is. Which button do you press? Most people probably say: "press up" since they want to go up. Not long ago I watched someone do the opposite and questioned them about their behavior. They said: "well the elevator is on the fifth floor and I am on the third, so I want it to come down to me". Much can be learnt about the design of user interfaces by considering this, apparently, simple interface. If you think about the elevator button problem you'll find that something so simple has hidden depths. How do people learn about elevator calling? What's the right amount of