if the application is huge it is becaus it was not been optimized.
if the application was not optimized (and so is huge, have a large
footprint),
it became fat and slow.
Wrong. Binary size and speed are two different things. Sometimes faster
means more code!
Do you remember AppleWorks ? The one who rans in the Apple II computers ?
The
one who was running in a 800KB floppy disk with enough room to add the OS
(ProDOS) and enough room to save data in the same floppy ?
In some way I compare Apple and Oranges since that AppleWorks didn't have
a
graphical interface, but the other AppleWorks (AppleWorks GS) had a
graphic
interface and ran on a less than 3MHz computer and needed only 1MB of
RAM...
For the record, it was the team that wrote AppleWorks GS who wrote the
Macintosh
AppleWorks 1 version... Do you remember the size of that version ? (less
than
1MB)...
Do you remember how little it could actually do?
The RB framework does a lot, and a lot was added in 200x. So the final
binary size increased. If you don't need the features and services of RB's
framework, write a tight little console program in C and see how small you
can get.
Daniel L. Taylor
Taylor Design
Computer Consulting & Software Development
[EMAIL PROTECTED]
www.taylor-design.com
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
