From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] linux stats in last year from linuxcon
Date: Mon, 21 Sep 2009 19:02:02 +0200 [thread overview]
Message-ID: <20090921170202.GA1306@polynum.com> (raw)
In-Reply-To: <13426df10909210922k6dec156ax1051cfe28a00b463@mail.gmail.com>
On Mon, Sep 21, 2009 at 09:22:56AM -0700, ron minnich wrote:
> 2.7M lines last year
> 10K lines added a day.
> 5K lines deleted per day.
>
> I keep thinking this can't be sustained. What happens next?
Are there stats indicating where the lines are added? If this is new
hardware (drivers), the accumulation is not a problem---if the API stays
stable; if one needs to rework all the drivers because the API does not
stabilized...
The only time I had to dive in the Linux kernel code, I was disappointed
by the "entropy" of the style and ended grep'ing or awk'ing all around
to extract a (partial) list of PCI identifiers and drivers. (This was
long ago now. 2002 ?)
I wonder if a software project will some day be an example of a black
hole: collapsing from its own size, the work needed to just make it work
being greater than the resources available and the gain to have it
work; and the inability to understand the whole (too much, too long)
resulting in the impossibility to evolve...
--
Thierry Laronde (Alceste) <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
next prev parent reply other threads:[~2009-09-21 17:02 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 16:22 ron minnich
2009-09-21 16:44 ` Patrick Kelly
2009-09-21 17:04 ` erik quanstrom
2009-09-21 17:29 ` Patrick Kelly
2009-09-21 17:02 ` tlaronde [this message]
2009-09-21 17:20 ` Patrick Kelly
2009-09-30 13:22 ` Ethan Grammatikidis
2009-09-21 17:41 ` Jack Norton
2009-09-21 17:53 ` Patrick Kelly
2009-09-21 19:32 ` David Leimbach
2009-09-21 19:42 ` Patrick Kelly
2009-09-22 1:12 ` andrey mirtchovski
2009-09-22 1:26 ` Patrick Kelly
2009-09-22 2:33 ` erik quanstrom
2009-09-22 2:52 ` andrey mirtchovski
2009-09-22 2:58 ` Patrick Kelly
2009-09-22 3:02 ` erik quanstrom
2009-09-22 6:15 ` Tim Newsham
2009-09-22 14:23 ` erik quanstrom
2009-09-22 16:57 ` Tim Newsham
2009-09-22 13:48 ` Eric Van Hensbergen
2009-09-22 14:44 ` David Leimbach
2009-09-22 14:39 ` David Leimbach
2009-09-22 14:47 ` erik quanstrom
2009-09-22 15:04 ` David Leimbach
2009-09-22 15:14 ` erik quanstrom
2009-09-22 16:26 ` David Leimbach
2009-09-22 3:36 ` ron minnich
2009-09-22 3:38 ` ron minnich
2009-09-22 14:17 ` J.R. Mauro
2009-09-22 14:47 ` David Leimbach
2009-09-22 20:14 ` Richard Uhtenwoldt
2009-09-22 20:47 ` Jack Norton
2009-09-22 22:31 ` Patrick Kelly
2009-09-23 1:55 ` David Arnold
2009-09-24 14:21 ` Patrick Kelly
2009-09-24 15:46 ` Jacob Todd
2009-09-24 15:56 ` Iruata Souza
2009-09-28 3:35 ` Patrick Kelly
2009-09-22 20:55 ` Chad Brown
[not found] <<Pine.BSI.4.64.0909220654020.23231@malasada.lava.net>
2009-09-22 17:13 ` erik quanstrom
2009-09-22 18:27 ` David Leimbach
2009-09-22 22:13 ` Tim Newsham
2009-09-22 22:25 ` Tim Newsham
2009-09-22 22:44 ` Jason Catena
[not found] <<012201ca3fec$c58f6020$50ae2060$@com>
2009-09-28 3:38 ` erik quanstrom
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=20090921170202.GA1306@polynum.com \
--to=tlaronde@polynum.com \
--cc=9fans@9fans.net \
/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).