Limiting ourselves to actual real-world scenarios (nobody is going to use an
Android phone for a Safety Critical control system like your cars brakes.),
none of those data variations have anything to do with how the data is
delivered.
On Wed, Jan 12, 2011 at 10:47 PM, Bob Kerns r...@acm.org
You weren't paying attention.
I was using illustrative examples, chosen mostly for 10-byte -- but
these issues show up all the time in all kinds of programming, from
enterprise to consumer utilities, to games.
And you didn't say that 10 bytes is just 10 bytes for Android, but not
for safety
And that is a very nice philosophical discussion of data in general.
Still doesn't help any with my original question, and the only implication I
can take from it is that you are assuming I'm a total neophyte programmer
who has no idea what his data is going to be used for, or what it is.
How
No, I didn't take you for a neophyte programmer. I won't apply any
adjectives; I'll just note that you're clearly the type of programmer
who would question why Mark would wonder, about the data (and thus its
implications on requirements, which you finally acknowledge) before
attempting to answer
Oh, easy question!
10 bytes of data when it's describing your current brake pedal
pressure is very different than 10 bytes describing the high score to
ultimately post on a web site somewhere when it gets around to
updating. It makes a real difference how quickly and reliably the data
is
5 matches
Mail list logo
