From: walter harms <wharms@bfs.de>
To: Patrick Ouellette <pouelle@debian.org>
Cc: linux-hams@vger.kernel.org
Subject: Re: Node.js and it's future in debian
Date: Fri, 04 May 2012 09:38:57 +0200 [thread overview]
Message-ID: <4FA38791.9030004@bfs.de> (raw)
In-Reply-To: <20120502200426.GF7390@flying-gecko.net>
Am 02.05.2012 22:04, schrieb Patrick Ouellette:
> On Wed, May 02, 2012 at 12:13:49PM -0500, Jonathan Nieder wrote:
>> Patrick Ouellette wrote:
>>
>>> Likewise I can argue the number of people with installed ham radio systems
>>> is a good reason NOT to change the current situation.
>>
>> You can, yes. But how does that move things forward at all?
>
> I never said it did. Clearly both sides have valid reasons to
> not change. Equally clear to me is one side ignored policy
> and created an issue to attempt to force a resolution they hope
> will be in their favor rather than solve the issue first.
>
>>
>> This is not supposed to be a popularity contest. I mentioned the
>> large pile of scripts because _every one of them would have to be
>> changed_ to have a working system. By contrast, there are two
>> configuration files mentioned so far that refer to /usr/sbin/node.
>
> The scripts (on either side) could be changed with a scripted change.
>
> If it is so simple to change the configuration files for the ham radio
> users, why has not a Node.js person put forth code to do this and advocated
> it on debian-hams and linux-hams? (The "patch" sent does not address
> automatically updating anything)
>
> I've discussed it with other ham radio operators. They shudder at the
> thought of changing the name because of the possible issues that will
> come up.
>
>>
>> [...]
>>> If it were "easy" to get an exception, why has this not already happened?
>>
>> Because you did not ask for one. Instead you have been wasting time
>> arguing and defending against an opponent you seem to assume is not
>> going to care or listen to you.
>
> The Node.js people apparently didn't ask for one either
> pot - kettle - black
>
> As for the last line, if I thought the opponent did not care or was
> not going to listen I would not waste the time putting forth my
> position. Since it would seem that is where we are, I won't
> continue to waste my time.
>
> Here is my proposal:
> Node.js people, put forth a reasonable and workable plan to allow
> hundreds or thousands of ham radio users to transition from
> /usr/sbin/node to /usr/sbin/axnode, including reliable shell scripts
> to verify all the files on the system are identified and allowed to
> be patched or manually modified. You created the situation, you
> provide the manpower to resolve it in the way you prefer.
>
>
hi par,
the problem of scripts would dissolve with time. I am worried about node.js itself.
I do think js is a problem not a solution, my experience with webservices is like
that described with other on the net .. slow, ugly, unmaintainable in the long run.
Unfortunately there is now a tendency in programming that everything should go web
and that understanding of code and algorithms is not longer important since fast
computers will make every rubbish look like usable.
My only hope is that even perl was unable to displace shell programming and this
time it will not work either.
re,
wh
prev parent reply other threads:[~2012-05-04 7:38 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
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 [this message]
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=4FA38791.9030004@bfs.de \
--to=wharms@bfs.de \
--cc=linux-hams@vger.kernel.org \
--cc=pouelle@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox