From: Gordon JC Pearc e <gordonjcp@gjcp.net>
To: linux-hams@vger.kernel.org
Cc: debian-hams@lists.debian.org, node@packages.debian.org,
nodejs@packages.debian.org
Subject: Re: Node.js and it's future in debian
Date: Thu, 03 May 2012 20:48:24 +0100 [thread overview]
Message-ID: <4FA2E108.2060806@gjcp.net> (raw)
In-Reply-To: <20120503185129.GA18768@burratino>
On 03/05/12 19:51, Jonathan Nieder wrote:
. Which package should use the name "node" in the long term? What
> can we do to ensure that happens eventually?
>
> (My answer is that I hope that neither uses the name "node" in
> the long term.)
Exactly. It's a stupidly common term, probably only slightly better
than calling it "program".
I don't buy into this idea that changing it will break all sorts of
legacy scripts. If they are that fragile and undocumented, *get rid of
them*! Undocumented fragile code is a liability. Kill it now, under
"known" circumstances, and fix it up properly.
--
Gordonjcp MM0YEQ
next prev parent reply other threads:[~2012-05-03 19:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACxjfDH5zYth6Q-ZDLDafqNEczbF3BqaGRcAhsaiPEnApbiUuA@mail.gmail.com>
[not found] ` <20120501205524.GI30521@flying-gecko.net>
[not found] ` <20120501215305.GA1250@burratino>
[not found] ` <20120501221659.GA11430@flying-gecko.net>
[not found] ` <20120502065003.GB2410@burratino>
[not found] ` <20120502165031.GC7390@flying-gecko.net>
[not found] ` <20120502171349.GA23806@burratino>
2012-05-02 20:04 ` Node.js and it's future in debian Patrick Ouellette
2012-05-02 20:31 ` Jonathan Nieder
2012-05-03 15:29 ` David Ranch
2012-05-03 15:33 ` David Ranch
2012-05-03 16:17 ` Marius Petrescu
2012-05-03 17:08 ` Patrick Ouellette
2012-05-03 17:05 ` Patrick Ouellette
2012-05-03 18:51 ` Jonathan Nieder
2012-05-03 19:48 ` Gordon JC Pearc e [this message]
2012-05-03 23:10 ` Hans-Peter F. Oeste
2012-05-04 4:09 ` David Ranch
2012-05-04 4:28 ` Ray Wells
2012-05-04 4:46 ` Jonathan Nieder
2012-05-04 12:31 ` DL1SIG
2012-05-04 13:29 ` [Pkg-javascript-devel] " Emilien Klein
2012-05-04 14:31 ` Patrick Ouellette
2012-05-04 7:38 ` walter harms
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=4FA2E108.2060806@gjcp.net \
--to=gordonjcp@gjcp.net \
--cc=debian-hams@lists.debian.org \
--cc=linux-hams@vger.kernel.org \
--cc=node@packages.debian.org \
--cc=nodejs@packages.debian.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.