On Tue, 10 Sep 2013 10:07:48 -0400, Francois Labreque wrote:

>> Even a /minor/ change to the code (say to make disk space reports not
>> turn up negative numbers) requires regression testing to make sure it
>> doesn't break anything else.  *Trivial* stuff being fixed, done by
>> large software companies, certainly, is not actually a trivial thing.
>>
>>
> That's why I'm saying it would have made more sense to implement the
> full specification the first time, instead of arbitrarily setting a
> limit way below the actual limit.

Yeah, I'm not arguing that point.  Fixing it, though, is another matter 
altogether.

The limitation /is/ stupid, especially since it's so easily worked around.

Jim

Post a reply to this message