9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Paul Lalonde <plalonde@telus.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] gnupg or pgp for plan9?
Date: Tue, 28 Mar 2006 18:07:42 -0800	[thread overview]
Message-ID: <3D71DABB-0EFE-4A27-B6AD-73B59B2BFB80@telus.net> (raw)
In-Reply-To: <facca0919a3c871e40ec39b28adccfa8@terzarima.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On 28-Mar-06, at 9:29 AM, Charles Forsyth wrote:

>> ( gnupg and those
>> tools are really big,
>
> why are they so big?
> silly question, probably.
>

Some years ago I had to drop a new graphics engine into an existing
code base.  Their performance was hideous, using up something
ridiculous like 30% of the frame time between the calls to "draw
player" and the call into my library.

A little excavation found 15 (yes, 15) layers of inheritance goop -
everything from a player face manager to an rendering object manager,
to a directX-look-alike graphics layer that had all been glommed into
the code base over only 3 years of evolution.  One sharp razor later
it was down to (a still unacceptable) 5%, with the rest back for
graphics submission.  Most of the code goop was stuff that could have
been done statically once if not for trying to make it fit the
previous layer of wrappers.

It happens because engineers are too lazy or scared to try to
understand the code they are modifying, and a layer seems safer.  My
case was 3 years of 2 code teams.  Imagine 10 years of open-source-
like distributed development :-(

Paul

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFEKevvpJeHo/Fbu1wRAgv9AKCij0PwgoGL9uf669VmTtI+q/x40ACglJZd
NlTYcfCSPrhxIRozt6/r820=
=/kax
-----END PGP SIGNATURE-----


  parent reply	other threads:[~2006-03-29  2:07 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-28  0:48 erik quanstrom
2006-03-28 14:59 ` Anthony Sorace
2006-03-28 15:23   ` Bruce Ellis
2006-03-28 15:57 ` Gabriel Diaz
2006-03-28 17:29   ` Charles Forsyth
2006-03-28 17:47     ` Gabriel Diaz
2006-03-29  0:27       ` Fernan Bolando
2006-03-29  2:49         ` geoff
2006-03-29  7:29           ` geoff
2006-03-29  2:07     ` Paul Lalonde [this message]
2006-03-29  3:17       ` quanstro
2006-03-29  3:56         ` Paul Lalonde
2006-03-29  9:09       ` Taj Khattra
2006-03-29 16:02         ` uriel
2006-03-29 22:03           ` Taj Khattra
  -- strict thread matches above, loose matches on Subject: below --
2006-03-29  1:13 erik quanstrom
2006-03-27  4:30 Fernan Bolando
2006-03-27  6:50 ` geoff
2006-03-27  7:25 ` Steve Simon
2006-03-27  9:18   ` Fernan Bolando
2006-03-27 13:10     ` Lluís Batlle
2006-03-27 17:26       ` Fernan Bolando
2006-03-28  0:38     ` Anthony Sorace
2006-03-28 13:59   ` Eric Grosse

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=3D71DABB-0EFE-4A27-B6AD-73B59B2BFB80@telus.net \
    --to=plalonde@telus.net \
    --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).