Gnus development mailing list
 help / color / mirror / Atom feed
From: Tommy Kelly <tommy.kelly@verilab.com>
To: ding@gnus.org
Subject: Re: What's wrong with this fancy split?
Date: Wed, 22 Dec 2010 06:26:00 -0600	[thread overview]
Message-ID: <m2wrn26lk7.fsf@verilab.com> (raw)
In-Reply-To: <m239pq2ijo.fsf@igel.home>

Andreas Schwab <schwab@linux-m68k.org> writes:

> Steinar Bang <sb@dod.no> writes:
>
>> In three words: keep it simple
>
> Then you should not use Gnus.

That seems like a bit of a non sequitur. And in fact to be honest it
risks being simply a cop  out. Being as simple *as possible* is a sign of
enginering and programming excellence. As Fred Brooks said, complexity
is our business. So there's no need to add more of it ourselves.

If that's not the case then here are some suggestions:

a. Remove the documentation. All of it.
b. Remove all the code comments
c. Obfuscate all the lisp
d. Encrypt it
e. Let everyone answer all questions on this list in Esperanto. Do that
until a majority are fluent in that language, then switch to
Aramaic. Then Coptic. Keep changing as long as it takes to ensure that
things are never simple.

Tommy




  parent reply	other threads:[~2010-12-22 12:26 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-21 22:29 Tommy Kelly
2010-12-21 22:41 ` Andreas Schwab
2010-12-21 23:50   ` Russ Allbery
2010-12-22  0:17     ` Tommy Kelly
2010-12-22  9:32     ` Andreas Schwab
2010-12-22 10:16       ` Steinar Bang
2010-12-22 10:28         ` Andreas Schwab
2010-12-22 10:35           ` Steinar Bang
2010-12-22 10:44             ` Andreas Schwab
2010-12-22 11:44               ` Bjørn Mork
2010-12-22 12:26               ` Tommy Kelly [this message]
2010-12-22 12:37                 ` Tassilo Horn
2010-12-22 12:59                   ` Tommy Kelly
2010-12-22 13:48                     ` Steinar Bang
2010-12-22 16:10                       ` Tommy Kelly
2010-12-22 17:46                         ` Steinar Bang
2010-12-22 18:19                           ` Tommy Kelly
2010-12-22 19:15                             ` Steinar Bang
2010-12-22 19:53                               ` Tommy Kelly
2010-12-22 22:12                                 ` Steinar Bang
2010-12-22 23:31                                   ` Tommy Kelly
2010-12-23 19:05                                     ` Steinar Bang
2010-12-22 15:39               ` Richard Riley
2010-12-22 12:34           ` Tommy Kelly
2010-12-22  0:13   ` Just shoot me now (was Re: What's wrong with this fancy split?) Tommy Kelly
2010-12-22  7:24     ` Just shoot me now Reiner Steib
2010-12-22 13:57       ` Richard Riley
2010-12-22 14:18         ` Tommy Kelly
2010-12-22 15:54           ` Sivaram Neelakantan
2010-12-22 16:30             ` Tommy Kelly
2010-12-22 16:54               ` Richard Riley
2010-12-22 17:12                 ` Tommy Kelly
2010-12-22 17:14                 ` Lawrence Mitchell
2010-12-22 17:43                   ` Richard Riley
2010-12-22 18:07                   ` Tommy Kelly
2010-12-22 22:40                   ` Richard Riley
2010-12-22 19:25           ` Eric S Fraga
2010-12-22  7:26     ` Just shoot me now (was Re: What's wrong with this fancy split?) Richard Riley
2010-12-22  9:35     ` Andreas Schwab
2010-12-22 12:53       ` Tommy Kelly
2010-12-22 18:21         ` Adam Sjøgren
2010-12-22 19:12           ` Tommy Kelly
2010-12-22 19:44             ` Adam Sjøgren

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=m2wrn26lk7.fsf@verilab.com \
    --to=tommy.kelly@verilab.com \
    --cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).