🚀 go-pugleaf

In <43k6m0$m3e@toon.ctp.com>, pdrap@ctp.com (Patrick Draper) writes:
>drj@peak.org (David Jenkinson) wrote:
>
>>In article <tonyn-0109950144230001@tonyn.tiac.net>, tonyn@tiac.net says...
>>>Deterministic real-time processing is difficult to do with interrupts. 
>>>You really can't tell when all the interrupts will stack up at the same
>>>time, causing the lowest priority interrupt to wait a long time.  Coupled
>>>with the overhead of context switching, this makes interrupt-driven
>
><<<snip>>>
>
>>Who the hell do you think is going to understand this bullshit?  Geez, dude, 
>>you should get a part on star trek.  You do excellent techo-babble.
>
>I understand it perfectly. But then again, you may not be the captain of
>your own starship like I am.
>
>
> /\/\ |Patrick Draper                        Mr. Order, he runs at a|
>/ /_.\|Cambridge Technology Partners, Inc.      good pace, but old  |
>\  /./|e-mail: pdrap@ctp.com                      Mother chaos is   |
> \/\/ |Amsterdam, The Netherlands                 winning the race. |
>
What sort of dimwit would be perusing this newsgroup without a basic understanding
of terms as simple as deterministic-real time processing, and context switching??
Probably some retard wanna be jock that has finally learned where the on switch is
on a computer and hunts and pecks to make his "grand" statements.  Get a clue
Turkey, the age of the computer elite is upon us.  Either cope, adapt, evolve or DIE!!

Ali