9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "boyd, rounin" <boyd@insultant.net>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] A prick into the wasps' nest ;-)
Date: Thu, 10 Jun 2004 05:25:23 +0200	[thread overview]
Message-ID: <058e01c44e9a$93e22ce0$9b7f7d50@SOMA> (raw)
In-Reply-To: <32902.67.85.61.176.1086855381.squirrel@www.infernopark.com>

> i am wondering if the wide popularity of DVD players followed by the
> quality improvement makes you think so.

humans can cope with with a a few missed frames.  there are many 
factors involved.  if we assume that TV is 26 (iirc) frames/second
there is phosphor persistance on the the screen (let's forget about
LCD's) and (iirc) there's retinal persistance.  so, dropping a
few frames  doesn't really matter.  oh yeah, it's interleaved as
well.

they may not even be watching when the frames are dropped.

if yer talking about military or medical systems they have to
be 'right on time' within certain tolerances.  otherwise yer
F-16 turns into an unflyable mess or your patient dies.

if you wanna build a 'real time' system:

    1. define it
    2. design it
    3. code it
    4. test it till it breaks and should it, goto 1

otherwise, pick up a hammer and go search for some (soft) approximation of a nail's position.

btw: as Seigfried said "WE DON'T DO THAT AT KAOS"



  reply	other threads:[~2004-06-10  3:25 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040609125113.UCQG24541.imf23aec.mail.bellsouth.net@Xaplos>
     [not found] ` <4fa4328626f76766f4799367fc0550c7@vitanuova.com>
2004-06-09 18:41   ` boyd, rounin
2004-06-10  8:16   ` vdharani
2004-06-10  3:25     ` boyd, rounin [this message]
2004-06-10  5:45       ` Nigel Roles
2004-06-10  9:20         ` Steve Simon
2004-06-10  9:20         ` Bruce Ellis
2004-06-10 14:55         ` boyd, rounin
2004-06-10  9:43 Andrew Simmons
2004-06-10 10:36 ` Nigel Roles
     [not found] <40C6C916.5080004@chunder.com>
2004-06-09 15:04 ` Mark F Rodriguez
2004-06-09 16:04   ` Bruce Ellis
2004-06-09 16:08     ` rog
2004-06-09 16:11       ` Bruce Ellis
2004-06-09 18:54   ` boyd, rounin
  -- strict thread matches above, loose matches on Subject: below --
2004-06-08  6:51 cej
2004-06-08  8:17 ` Vladimir Los
2004-06-09 23:10   ` kim kubik
2004-06-09 23:22     ` boyd, rounin
2004-06-09 23:40       ` George Michaelson
2004-06-09 23:41         ` boyd, rounin
2004-06-09 23:41       ` andrey mirtchovski
2004-06-09 23:44         ` boyd, rounin
2004-06-09 23:55           ` Geoff Collyer
2004-06-09 23:27     ` rog
2004-06-10  8:03     ` Vladimir Los
2004-06-07  7:09 cej
2004-06-07 15:53 ` Rob Pike
2004-06-08  7:32   ` Vladimir Los
2004-06-08 18:18     ` Sape Mullender
2004-06-08 18:55       ` Mark F Rodriguez
2004-06-08 18:58         ` William Josephson
2004-06-08 19:05         ` rog
2004-06-08 19:39           ` Mark F Rodriguez
2004-06-08 20:50             ` boyd, rounin
     [not found]     ` <40C6C6E8.1000302@chunder.com>
2004-06-20 22:35       ` vdharani

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='058e01c44e9a$93e22ce0$9b7f7d50@SOMA' \
    --to=boyd@insultant.net \
    --cc=9fans@cse.psu.edu \
    /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).