From: "Lyndon Nerenberg (VE6BBM/VE7TFX)" <lyndon@orthanc.ca>
To: 9fans@9fans.net
Subject: [9fans] ports duplication
Date: Sun, 7 Mar 2010 12:49:51 -0700 [thread overview]
Message-ID: <4d33d2aa22b5c83c1e4348c73d008097@yyc.orthanc.ca> (raw)
I really think this idea that duplication of things in contrib is bad,
is bad (or just a red herring).
For ports of big applications (python, say), the amount of work involved
is going to self-limit the number of ports right up front. And the ones
that do make it will self-select based on the quality of the port.
As for the smaller things, I would prefer to see ten different bits of
code that achieve the same end vs. just one. Diversity is good, and a
broader selection of code gives a bigger field to mine for ideas and
concepts.
--lyndon
next reply other threads:[~2010-03-07 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-07 19:49 Lyndon Nerenberg (VE6BBM/VE7TFX) [this message]
2010-03-07 20:02 ` Eric Van Hensbergen
2010-03-08 4:26 ` lucio
2010-03-08 12:17 ` Iruata Souza
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=4d33d2aa22b5c83c1e4348c73d008097@yyc.orthanc.ca \
--to=lyndon@orthanc.ca \
--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).