RE: MIME as an appointment element separator - good move...

[Alec Dun <AlecDu@xxxxxxxxxxxxxxxxxxxxxx>]

I understand.  It's a tradeoff between memory usage and backward
compatibility.

Thanks,
Alec.

> ----------
> From: 	Ken Shan[SMTP:ken@digitas.org]
> Sent: 	Monday, December 9, 1996 9:07 AM
> To: 	Alec Dun
> Cc: 	Paul.Rarey@Clorox.com; ietf-calendar@imc.org
> Subject: 	Re: MIME as an appointment element separator - good
> move...
> 
> Alec Dun wrote:
> 
> > The point is that the code is unnecessary.
> 
> The point is that breaking compatibility with existing code is
> unnecessary.
> 
> > The unnecessary memory that is consumed here can not be used by
> other
> > apps.  The number of apps and amount of data I can use on my machine
> > will be reduced by the additional code.  If all the apps running on
> my
> > machine have the drawback of poor code reuse, then it makes a
> > significant difference.
> 
> I don't see how having very slightly extra code in one particular
> application automatically leads to all apps running on your machine
> suddenly starting to have the drawback of poor code reuse.
> 
> -- 
> blue | Ken; Shan, Chung-chieh; Sian7, Tiong1-kiat8;
> ken@digitas.harvard.edu.
>  ()  | Your code today becomes the mind tomorrow:  Your plan its
> means,
>  /\  | your dream its ends, your ideal its elegance.  Hack on.
>