🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.folklore.computers
Article #620835

Re: Implementation of a Turing Machine?

#620835
From: Peter Flass
Date: Wed, 21 Feb 2018 21:20
56 lines
3429 bytes
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?
> 

Predicting eclipses, IIRC.

-- 
Pete
Technical Details
Message-ID: <11021708.540940715.254554.peter_flass-yahoo.com@news.eternal-september.org>
Path: mbox-mo1.pugleaf.net!o9ni7131qte.1!nntp.google.com!goblin1!goblin2!goblin.stu.neva.ru!aioe.org!eternal-september.org!feeder.eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
References: <55cr8dd6kn7hl2b5dat7s74o13beb2946v@4ax.com> <201802211011054696-mlevinespmfltr@redshift.com> <qsdr8d92ofeqom41pd79lc4cdvovl3ffq4@4ax.com> <slrnp8rnjj.6c7.mausg@deb.xxx>

Show Full Headers
Complete Article Headers
X-Received: by 10.55.31.41 with SMTP id f41mr3433292qkf.51.1519248010919;        Wed, 21 Feb 2018 13:20:10 -0800 (PST)
X-BeenThere: alt.folklore.computers@googlegroups.com
Received: by 10.55.77.8 with SMTP id a8ls1396674qkb.3.gmail; Wed, 21 Feb 2018 13:20:09 -0800 (PST)
X-Received: by 10.55.130.7 with SMTP id e7mr3461376qkd.9.1519248009794;        Wed, 21 Feb 2018 13:20:09 -0800 (PST)
Path: mbox-mo1.pugleaf.net!o9ni7131qte.1!nntp.google.com!goblin1!goblin2!goblin.stu.neva.ru!aioe.org!eternal-september.org!feeder.eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: Peter Flass <peter...@yahoo.com>
Newsgroups: alt.folklore.computers
Subject: Re: Implementation of a Turing Machine?
Date: Wed, 21 Feb 2018 14:20:09 -0700
Organization: A noiseless patient Spider
Lines: 56
Message-ID: <11021708.540940715.254554.peter_flass-yahoo.com@news.eternal-september.org>
References: <55cr8dd6kn7hl2b5dat7s74o13beb2946v@4ax.com> <201802211011054696-mlevinespmfltr@redshift.com> <qsdr8d92ofeqom41pd79lc4cdvovl3ffq4@4ax.com> <slrnp8rnjj.6c7.mausg@deb.xxx>
Mime-Version: 1.0
Injection-Info: reader02.eternal-september.org; posting-host="c63fcd5e48f85797345d323f61825d3a"; logging-data="29090"; mail-complaints-to="ab...@eternal-september.org"; posting-account="U2FsdGVkX19RHnGLFFQS/mO8V/ptepsW"
User-Agent: NewsTap/5.3.1 (iPad)
Cancel-Lock: sha1:rs6HnzzJLMvGtg3+naYfWgBSjlg= sha1:Ti1i/8pd116lctM1YKFN7VHQC40=
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit