| 1 |
On Sun, 30 Mar 2014 12:39:56 -0400 |
| 2 |
Rich Freeman <rich@××××××××××××××.net> wrote: |
| 3 |
> On Sun, Mar 30, 2014 at 12:31 PM, Ciaran McCreesh |
| 4 |
> <ciaran.mccreesh@××××××××××.com> wrote: |
| 5 |
> > On Sun, 30 Mar 2014 12:27:34 -0400 |
| 6 |
> > Rich Freeman <rich0@g.o> wrote: |
| 7 |
> >> As soon as you start getting into anything that involves the real |
| 8 |
> >> world and engineering |
| 9 |
> > |
| 10 |
> > Which isn't the case here, so this whole thing is irrelevant. |
| 11 |
> |
| 12 |
> What prevents the output of a tool from being used in an engineering |
| 13 |
> context? In any case, my concern is more with ambiguity (when |
| 14 |
> software tells me I have 1GB of free space, what does that mean?). I |
| 15 |
> think GB are more useful than GiB in most cases (though I explicitly |
| 16 |
> stated in my first proposal that there are situations where this isn't |
| 17 |
> the case), but I care more about ambiguity. |
| 18 |
|
| 19 |
When you're told you'll need 1GB of disk space, if you have exactly 1GB |
| 20 |
+ 1 byte of disk space left then you need more disk space whichever way |
| 21 |
things are being measured. |
| 22 |
|
| 23 |
-- |
| 24 |
Ciaran McCreesh |
Archives