From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Advances in software technology
Date: Fri, 27 Aug 2004 10:04:32 -0600 [thread overview]
Message-ID: <Pine.LNX.4.60.0408270957360.3163@fbsd.cpsc.ucalgary.ca> (raw)
In-Reply-To: <412F0090.1000906@9fs.org>
somehow, the guy who wrote a flight simulator "in 1536 bytes of real code"
still remains my hero (ioccc's 98 contest, ioccc.org).
as for file sizes -- plan9's clock.c, which i modified slightly to compile
under plan9port yesterday, turned out to a binary of 2MB... at least it
occupies only 1.8MB ram :) go X!
andrey
prev parent reply other threads:[~2004-08-27 16:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 9:36 Nigel Roles
2004-08-27 10:36 ` dvd
2004-09-01 8:58 ` Aharon Robbins
2004-08-27 10:58 ` geoff
2004-08-27 13:27 ` Nigel Roles
2004-08-27 14:36 ` Jason Gurtz
2004-08-27 22:02 ` Joel Salomon
[not found] ` <salomo3@cooper.edu>
2004-08-28 10:51 ` Andrew Lynch
2004-08-27 16:04 ` andrey mirtchovski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.60.0408270957360.3163@fbsd.cpsc.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).