🚀 go-pugleaf

peter@NeoSoft.com (Peter da Silva) writes:
>englehar@src.honeywell.com (Matt Englehart) writes:
>tpaquette@ita.lgc.com (Trevor Paquette) writes:
>> >mccoy@gothamcity.jsc.nasa.gov (Daniel J. McCoy) writes:
>> >>bill@solaria (Bill Neisius) writes:
>> >>|>Douglas W O'Neal (doug@jhunix.hcf.jhu.edu) wrote:
>> >>|>:norm@bnr.ca writes:
>> >>|>:->bret@muppet.bt.co.uk (Bret Giddings) writes:
>> >>|>:->|> What! another clock for wimps. I use a real clock, one that displays the number
>> >>|>:->|> of seconds since Jan 1st 1970.
>> >>|>:->This is starting to sound like the "We were *so* poor..." skit from Monty
>> >>|>:->Python.  BTW, (let's see what I can come up with), *I* use the number of seconds
>> >>|>:->since Jan 1, 1970 but in Greenwich Mean Time :-)
>> >>|>:*I* use the number of seconds since Nov 17, 1858.  (I can't help it, I was
>> >>|>:raised on VMS and UN*X time doesn't come naturally to me.)
>> >>|>Oh yeah? MY clock counts from January 1, 4713 B.C. (start of the 
>> >>|>astronomical Julian calendar)
>> >>>OH YEAH???  My clock counts seconds backwards from Star Date 938943.1299,
>> >>>the second coming of Jesus.
>> >> Pah! Child's play.  *My* clock sends pulses direct to a composite screen on my
>> >>retina via electrodes crimped into my skull which receive sync from a transmitter
>> >>on my Moulinex food processor.
>> >  HA! My clock actually displays the current astronomical sky and I have to 
>> > figure out the time from the star patterns and placements!
>> 
>> HA! My clock actually displays the current astronomical sky from a random
>> location in the galaxy, and I have to figure out the time from the star
>> patterns and placements!
>
>Well, I started to make a clock from one of those "build a working paper
>clock" books, but I got carried away. It's now a complete working paper
>Analytical Engine, and I run an 80386 simulator on that. I'm booting 386BSD
>now, and in a couple of years when it comes up I'll have Xclock running.
>I don't think it's going to keep very good time, though... I keep getting
>silo overflows reading WWV at 110 baud. I guess I'll need to build a paper
>16550 to fix that.
>
>Which Xclock should I use?

How 'bout one written in PostScript; sure you'd have to go
pick-up hardcopy every time you wanted to know the time & it
would consume enormous amounts of paper if you wanted updates
every second, but you'll have to agree it'd be really neat...

--
elf@ee.ryerson.ca