[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: MCL support for MOP
- To: email@example.com, firstname.lastname@example.org
- Subject: Re: MCL support for MOP
- From: email@example.com
- Date: Sun, 10 Jan 93 02:36:49 -0600
- Cc: firstname.lastname@example.org
> Feedback please. Do you need these facilities? Other ideas?
> The MCL development team has decided that MCL's size is not the
> most important thing we have to work on right now, but it's
> still important to us.
you may have your reasons for _not_ being interested in the size
of applications generated by MCL, however, this is the primary
reason why I am not using MCL to develop any applications programs,
and I can't see myself doing so until that get's fixed. Why? well,
it looks stupid to deliver a simple program that takes up 1.4 megs.
especially when the same task can be done with a 20k application.
for example, BinHex (the application) takes up something like 8k
on disk, while the MCL BinHex application (which appears to do
the same thing, although slower) occupies well over 1 meg of disk
space, and it doesn't run well with less than two!
perhaps this is petty compared to the obvious advantages of using
MCL for development, but I feel these things are important. Generally,
I'd prefer to use MCL for everything, including the tasks normally
done by the finder, and for my own personal use it's great; but,
I'd find it difficult trying to explain to a client why a program
with the functionality of TeachText more than 1meg of disk space, and
runs with 2 or more megs in ram...