From ... Newsgroups: comp.lang.dylan,comp.lang.lisp,comp.lang.lisp.mcl Path: bga.com!news.sprintlink.net!howland.reston.ans.net!ix.netcom.com!netcom.com!netcom13.netcom.com!sgml From: Erik Naggum Subject: Re: A Dylan implemented on Common Lisp Message-ID: <3004385493.825773@naggum.no> Sender: sgml@netcom13.netcom.com Organization: Naggum Software; +47 2295 0313 References: <3jirll$r0g@cantaloupe.srv.cs.cmu.edu> <3k53lf$h25@news.cs.brandeis.edu> <3k5ko2$pc9@geraldo.cc.utexas.edu> Date: Thu, 16 Mar 1995 23:31:32 GMT Lines: 24 Xref: bga.com comp.lang.dylan:2244 comp.lang.lisp:5378 comp.lang.lisp.mcl:2015 [James McCartney] | The 'hello' application is 56K on disk, it has to load the Dylan | framework which is 524K, the main Dylan library 465K, the mac toolbox | library which is 57K. Time from double clicking the hello application | on the hard disk (I copied it all to the HD from the CD before running | it) until 'Hello, Dylan!' appears is 22 seconds on a PowerMac | 8100/80. When looking at 'About this Macintosh' in the Finder it | reveals that 'hello' is running in a 2000K partition which is about 75% | full. you may not recall that I tried to show the C fans that their "small footprint" C programs actually incur shared libraries, memory allocation, etc, on behalf of the program that rocket their 50K "disk image" into much larger memory images, and enjoy special operating system support that other languages will have to put in shared libraries. I guess the reason for the confusion is that people can't differentiate "program" from "process". programs sit on disk, processes run in memory. I think the latter is more important than the former, as disk is still _way_ cheaper than RAM, so I consider disk footprint to be red herring. # -- miracle of miracles. look what the Net dragged in.