The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] The birth of the Z3
Date: Sat, 12 May 2018 11:04:26 -0400	[thread overview]
Message-ID: <CAC20D2PdNM52dg8v_LJ_yF_3COocJG7afXbNd0uZhs5UEopkgA@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.999.1805120810571.79090@aneurin.horsfall.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2452 bytes --]

On Fri, May 11, 2018 at 6:21 PM, Dave Horsfall <dave at horsfall.org> wrote:

> Way back on this day in 1941, Conrad Zuse unveiled the Z3; it was the
> first programmable automatic computer as we know it (Colossus 1 was not
> general-purpose).  The last news I heard about the Z3 was that she was
> destroyed in an air-raid...
>
> This pretty much started computing, as we know it.


​Again be careful -- we don't want to go down that rat hole.   There has
been always been an argument since it (as well as Atanasoff and Aiken's
machines all) lacks a conditional branch.    Although, I do believe some
one the UK proved the Z3 to be Turing complete; but the argument will
always be there.

What I tell people is that Babbage theorized the computational device and
Lady Ada extended the theorized to general programmability  (to play music
I believe) but it was never built and she and Babbage argued a bit about
it.   The Loom folks demonstrated that the idea programmability was
possible.   Zuse put the two idea together and reduce it practice.

But .. until we also include a conditional branch the ability to do self
modify code we don't really have the machine with think of as the automatic
programmable computer.

Check out:
http://page.mi.fu-berlin.de/rojas/1993/Who_invented_the_computer.pdf its a
fun read.

There is a nice table in it:

Machine             Memory & CPU Separated           Conditional Branching
       Soft or Hard Programming      Support Self Modify    Indirect
Addressing
Babbage                   yes
    yes                                    soft
              proposed                      no
Zuse                          yes
         no                                    soft
                        no                           no
Atanasoff                   yes
       no                                    hard
                     no                          no
Aiken Mark1              no
    no                                    soft
                  no                           no
ENIAC                       no
       partial                              hard
                   no                          no
Manchester               yes
  yes                                    soft
                   yes                        no
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180512/29879436/attachment.html>


  reply	other threads:[~2018-05-12 15:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-11 22:21 Dave Horsfall
2018-05-12 15:04 ` Clem Cole [this message]
2018-05-13  6:52   ` Greg 'groggy' Lehey
2018-05-13 21:07     ` Clem cole
2018-05-13 21:30 Noel Chiappa
2018-05-13 21:44 ` Mike Markowski
2018-05-14  3:27   ` Dave Horsfall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAC20D2PdNM52dg8v_LJ_yF_3COocJG7afXbNd0uZhs5UEopkgA@mail.gmail.com \
    --to=clemc@ccc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).