🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.folklore.computers
Article #620837

Re: Implementation of a Turing Machine?

#620837
From: ma...
Date: Wed, 21 Feb 2018 23:05
70 lines
3626 bytes
On 2018-02-21, JimP <solo...@gmail.com> wrote:
> On 21 Feb 2018 21:02:43 GMT, maus <ma...@mail.com> wrote:
>
>>On 2018-02-21, JimP <solo...@gmail.com> wrote:
>>> On Wed, 21 Feb 2018 10:11:05 -0800, Michael LeVine
>>><mlevine...@redshift.com> wrote:
>>>
>>>>On 2018-02-21 17:48:34 +0000, Gene Wirchenko said:
>>>>
>>>>> On 21 Feb 2018 11:13:54 GMT, maus <ma...@mail.com> wrote:
>>>>> 
>>>>>> On 2018-02-20, Gene Wirchenko <ge...@telus.net> wrote:
>>>>>>> On Mon, 19 Feb 2018 09:11:12 +0000, Gareth's Downstairs Computer
>>>>>>> <headstone255.but.n...@yahoo.com> wrote:
>>>>>>> 
>>>>>>>> On 19/02/2018 07:26, Gene Wirchenko wrote:
>>>>>>> 
>>>>>>>> Not enough description of the state machine, though, for
>>>>>>>> each state need to know action if 1 or 0 read, whether to
>>>>>>>> write back 1 or 0, and next state whether 1 or 0 read.
>>>>>>>> 
>>>>>>>> It is particularly fascinating that a Turing Machine could
>>>>>>>> have been built with the technology available at the time
>>>>>>>> it was first postualted (1935?)
>>>>>>> 
>>>>>>> I do not think that that is that notable.  The machine could have
>>>>>>> been made back in Babbage's time.  (Too bad Babbage did not come up
>>>>>>> with something more immediately practical.)
>>>>> 
>>>>>> AFAIhaveread, the problem was that it not possible to machine parts to
>>>>>> the limits that Babbage's machines needed, at that time.
>>>>> 
>>>>>      I was thinking of that plus that Babbage did not get something
>>>>> practical going.  That might have helped get mechanical computing
>>>>> going big.
>>>>> 
>>>>> Sincerely,
>>>>> 
>>>>> Gene Wirchenko
>>>>
>>>>His difference engine was built tothe same tolerance's that were 
>>>>available in his time,
>>>>and it worked as designed.
>>>>https://www.youtube.com/watch?v=be1EM3gQkAY
>>>>https://www.youtube.com/watch?v=BlbQsKpq3Ak
>>>
>>> The antikythera mechanism was built to very tight tolerances and
>>> worked.
>>
>>CITE:?
>>
>>What was it for?
>
> I had no idea anyone in here didn't know what the anikythera mechanism
> was.
>
> http://antikythera-mechanism.gr/
>
> http://www.antikythera-mechanism.com/
>
> https://www.smithsonianmag.com/history/decoding-antikythera-mechanism-first-computer-180953979/
>
> https://www.livescience.com/1166-scientists-unravel-mystery-ancient-greek-machine.html
>
> And likely at least 50 more.


-- 
greymaus.ireland.ie
Just_Another_Grumpy_Old_Man
Technical Details
Message-ID: <slrnp8ruqe.2k6.mausg@smaus.org>
Path: mbox-mo1.pugleaf.net!o9ni2237qte.1!nntp.google.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
References: <55cr8dd6kn7hl2b5dat7s74o13beb2946v@4ax.com> <201802211011054696-mlevinespmfltr@redshift.com> <qsdr8d92ofeqom41pd79lc4cdvovl3ffq4@4ax.com> <slrnp8rnjj.6c7.mausg@deb.xxx> <kjrr8dhv1po68acrvs13dr2ooepk831fce@4ax.com>

Show Full Headers
Complete Article Headers
X-Received: by 10.55.32.10 with SMTP id g10mr3444579qkg.60.1519254352830;        Wed, 21 Feb 2018 15:05:52 -0800 (PST)
X-BeenThere: alt.folklore.computers@googlegroups.com
Received: by 10.55.239.14 with SMTP id j14ls1512113qkk.6.gmail; Wed, 21 Feb 2018 15:05:51 -0800 (PST)
X-Received: by 10.55.151.68 with SMTP id z65mr3609442qkd.30.1519254351355;        Wed, 21 Feb 2018 15:05:51 -0800 (PST)
MIME-Version: 1.0
Path: mbox-mo1.pugleaf.net!o9ni2237qte.1!nntp.google.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: ma...@mail.com
Newsgroups: alt.folklore.computers
Subject: Re: Implementation of a Turing Machine?
Date: 21 Feb 2018 23:05:50 GMT
Lines: 70
Message-ID: <slrnp8ruqe.2k6.mausg@smaus.org>
References: <55cr8dd6kn7hl2b5dat7s74o13beb2946v@4ax.com> <201802211011054696-mlevinespmfltr@redshift.com> <qsdr8d92ofeqom41pd79lc4cdvovl3ffq4@4ax.com> <slrnp8rnjj.6c7.mausg@deb.xxx> <kjrr8dhv1po68acrvs13dr2ooepk831fce@4ax.com>
X-Trace: individual.net mQak8UWT7RVUnlM8y/J5bQBIEfBEXS62SpmN7SxPpxVrKbETaH
Cancel-Lock: sha1:EW5e7icE70pE/TliI0gX/55tkjc=
User-Agent: slrn/1.0.2 (Linux)
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit