On Fri, Jul 20, 2012 at 3:07 PM, Joe Zeff <joe@xxxxxxx> wrote: > Very few programmers, any more, are taught to be frugal with memory. a good example of tight code was Image Alchemy, a shareware command line app for image conversion, for DOS, Win32, and also OS/2. It analyzed the image then did the conversion in chunks, DISK based not MEMORY based, it was all disk-bound. As a result you could be using a 8MB RAM DOS machine and perform image conversions that would take hundreds of megs of memory if loaded all at once. It was very popular with BBS operators. Yet, nowadays, there' s so much ram that most apps just load the whole bitmap in memory then do the conversion by copying the bitmap image to RAM too, so you end with multiple copies of the images on RAM at the same time. FC -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
