| From: | Erik Jameson <erikj@****.COM> |
|---|---|
| Subject: | Re: What's a megapulse? |
| Date: | Tue, 26 May 1998 20:21:09 -0400 |
> A better place to work from, IMO, is that an MP is an amount of
>PROCESSOR POWER consumed. This way, files take MP because they are like
>little java aplets that dislpay themselves (explaining both why platform
>compatability is an issue and you don't need any programs to read chips
>and such, and thier large size). Matrix utilities consume Deck
>procesing power (although MPCP limits the "power"of utilities, perhaps
>by limiting the instruction set availible). Other items are "burned"
>onto chips, easily being a demand on procesorers to use, not a "memeory
>size".
> Under this assumption, memeory is practically free (reasonable
>assumption), but processors have trouble with certain massive chunks of
>"bloatware" (also, unfortunatley, a reasonable assumption).
Ooooooh...that's an elegant solution from my standpoint.
Yes, MegaPulses probably were an abstraction created to avoid making
statements about computers that would be made obsolete and laughable in a
few years.
But for those that want to know, for whatever reason, this is a terribly
elegant solution. Without knowing too much about computers other than how
to use them, this appeals to me on so many levels.
I like it.
Erik J.
"Forgive me FASA for I have sinned. It has been 6 days since I last played
Shadowrun and 15 days since I last bought a SRTCG booster pack."
