From: despen@verizon.net
To: help-gnu-emacs@gnu.org
Subject: Re: What's the differences b/t M-x eshell and M-x shell.
Date: Sun, 10 Oct 2010 17:13:19 -0400 [thread overview]
Message-ID: <icvd59sqds.fsf@verizon.net> (raw)
In-Reply-To: i8t81q$knn$1@quimby.gnus.org
Richard Riley <rileyrg@googlemail.com> writes:
> despen@verizon.net writes:
>
>> Richard Riley <rileyrg@googlemail.com> writes:
>>
>>> despen@verizon.net writes:
>>>
>>>> Xah Lee <xahlee@gmail.com> writes:
>>>>
>>>>> Rather, i blame FSF... for various reasons, the culture of FSF... made
>>>>> it that way.
>>>>
>>>> Oh boy here you go again.
>>>>
>>>> The ONLY projects I ever worked on that were 100% harmonious were
>>>> projects I did by myself.
>>>>
>>>> I don't care if it's construction, software development, or
>>>> brain surgery. People inevitably develop conflicts and differences
>>>> of opinion.
>>>
>>> Of course. And work together to solve them. Did anyone say any
>>> different?
>>>
>>>> A good software developer learns how to work with others.
>>>> One of the things you have to do is accept others as imperfect.
>>>
>>> In defence of Xah Lee : Nowhere did he say otherwise.
>>
>> He did suggest that throwing the leader off the project
>> as a solution.
>
> He suggested that that leader causes hold ups in development. You
> clearly disagree. No where did he say that teams cant work successfully.
If you resort to throwing someone off a team,
you are taking the last resort. You've given up.
Blaming the culture is even more general.
It's like saying the whole team has to go.
I have no opinion about RMS.
>> More important, the THINKS he sees problems with the project and
>> blames the "culture". That's confrontational, that's not seeking
>> a solution.
>
> He suggested solutions. Whether I agree or not is immaterial. Putting
> words into his mouth and blindly supporting existing culture seems to
> reinforce his points rather than disprove them,
I don't know why you take what I said that way.
Banning someone is giving up.
I am only willing to judge by results.
Years ago, XEmacs was superior to Emacs.
Now it seems to me the Emacs team is firing on all cylinders.
They caught up to and surpassed XEmacs.
I also believe it's the responsibility of new-comers to adapt
to the team as it is.
If Xah has more to contribute than RMS, he could join the team
and show it by example. If he really believes it's impossible,
let him fork the code and draw his own team.
next prev parent reply other threads:[~2010-10-10 21:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54065fc0-bb58-46d7-bcb8-08fbc5e71286@y12g2000prb.googlegroups.com>
2010-10-09 12:49 ` What's the differences b/t M-x eshell and M-x shell Pascal J. Bourguignon
2010-10-09 21:27 ` Sean McAfee
2010-10-10 8:39 ` Xah Lee
2010-10-10 19:45 ` despen
2010-10-10 19:53 ` Richard Riley
2010-10-10 20:20 ` despen
2010-10-10 20:35 ` Richard Riley
2010-10-10 21:13 ` despen [this message]
2010-10-10 1:03 ` Xah Lee
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=icvd59sqds.fsf@verizon.net \
--to=despen@verizon.net \
--cc=help-gnu-emacs@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.