From: Wes Kussmaul <wes@authentrus.com>
To: 9fans@9fans.net
Subject: Re: [9fans] these are release of 9front?
Date: Tue, 8 Jan 2013 11:22:15 -0500 [thread overview]
Message-ID: <1357662135.2693.86.camel@wes-HP-Pavilion-g7-Notebook-PC> (raw)
In-Reply-To: <88a732387065dfe7d42050200dfc91c8@9front.org>
On Tue, 2013-01-08 at 07:48 -0600, sl@9front.org wrote:
> > There are plenty of things in Plan 9 still in need of improvement
> > or even rewriting. That's why it makes me sad to see our small
> > community being made even smaller when some of the most skilled
> > programmers direct their efforts into splintering off their own
> > little playgrounds instead of helping to make Plan 9 better for
> > everyone.
>
> So far as I know the only projects not sharing all their source
> code are semi-official ones.
The big leaps happen when someone with a different set of assumptions
from those of the creators of a thing see it fulfilling a different
function. Forking is messy, as are inflection points.
next prev parent reply other threads:[~2013-01-08 16:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 1:07 Francesco Cardi
2013-01-08 1:17 ` John Floren
2013-01-08 1:27 ` sl
2013-01-08 9:09 ` Richard Miller
2013-01-08 9:59 ` cinap_lenrek
2013-01-08 10:15 ` Richard Miller
2013-01-08 10:36 ` cinap_lenrek
2013-01-08 10:52 ` Richard Miller
2013-01-08 11:10 ` lucio
2013-01-08 11:24 ` Bence Fábián
2013-01-08 14:14 ` steve
2013-01-08 15:37 ` erik quanstrom
2013-01-08 13:48 ` sl
2013-01-08 16:22 ` Wes Kussmaul [this message]
2013-01-08 14:24 ` cinap_lenrek
2013-01-08 14:33 ` cinap_lenrek
2013-01-08 14:52 ` David Leimbach
2013-01-08 15:53 ` Nemo
2013-01-08 19:38 ` Richard Miller
2013-01-08 20:40 ` mveety
2013-01-08 20:48 ` erik quanstrom
2013-01-08 20:54 ` Matthew Veety
2013-01-08 22:42 ` Federico G. Benavento
2013-01-09 4:23 ` cinap_lenrek
2013-01-12 13:48 ` Richard Miller
2013-01-12 14:12 ` erik quanstrom
2013-01-12 14:35 ` Richard Miller
2013-01-12 14:47 ` Richard Miller
2013-01-08 19:18 ` 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=1357662135.2693.86.camel@wes-HP-Pavilion-g7-Notebook-PC \
--to=wes@authentrus.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).