9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Prof Brucee <prof.brucee@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Has Linux jumped the shark?
Date: Fri, 24 Jul 2015 22:05:53 +1000	[thread overview]
Message-ID: <CAJDwFdj-KD9LuQm0pV-_AHZ9ciRw+rwRkyTQE1Q269uQg+kcNQ@mail.gmail.com> (raw)
In-Reply-To: <cebaf26179555664ba15d7cefb6679a5@krabbe.dyndns.org>

[-- Attachment #1: Type: text/plain, Size: 1452 bytes --]

Look what I started. And All That Clever Code ...

Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are, by
definition, not smart enough to debug it.

        — Brian W. Kernighan <http://genius.cat-v.org/brian-kernighan/> and
P. J. Plauger in *The Elements of Programming Style*
<http://www.amazon.com/gp/product/0070342075?ie=UTF8&tag=catv-20&linkCode=as2&camp=1789&creative=390957&creativeASIN=0070342075>
.

On Fri, Jul 24, 2015 at 9:19 PM, Ingo Krabbe <ikrabbe.ask@gmail.com> wrote:

> Actually not all bugs are fixed, some are introduced as a feature
>
> http://intellivisionlives.com/bluesky/games/credits/space.html#hawk
>
>
> > On 24 July 2015 at 04:54, Prof Brucee <prof.brucee@gmail.com> wrote:
> >
> >> has Linux with the release of 4.0 finally jumped the shark.
> >
> >
> > Since it's called "Hurr Durr I'ma Sheep", I thought I'd ask a celebrity
> > what he thought of it.
> > The response was much as I'd expected: http://goo.gl/ZefDFV
> > Others simply said that "it was baaad".
> >
> > I'm amused that as usual, dynamic patching of kernel source, like
> replacing
> > dynamic libraries, is presented uniformly as a way to fix bugs everywhere
> > quickly, because we all know that bugs always are fixed and never
> > introduced, and being able to capture a kernel without rebooting is never
> > of practical interest.
>

[-- Attachment #2: Type: text/html, Size: 2925 bytes --]

  reply	other threads:[~2015-07-24 12:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-24  3:54 Prof Brucee
2015-07-24  4:49 ` cinap_lenrek
2015-07-24  5:10   ` Prof Brucee
2015-07-24  9:05     ` Tiago Natel
2015-07-24  9:27       ` Prof Brucee
2015-07-24 10:25         ` Ingo Krabbe
2015-07-24 13:07     ` erik quanstrom
2015-07-24 11:08 ` Charles Forsyth
2015-07-24 11:19   ` Ingo Krabbe
2015-07-24 12:05     ` Prof Brucee [this message]
2015-07-24 12:13       ` Ingo Krabbe
2015-07-24 12:34         ` Prof Brucee
2015-07-24 17:08       ` Devon H. O'Dell
2015-07-24 18:52         ` Charles Forsyth
2015-07-24 19:20           ` Devon H. O'Dell
2015-07-24 20:26             ` Charles Forsyth
2015-07-24 20:38             ` Prof Brucee
2015-07-24 20:57               ` Kurt H Maier
2015-07-25 10:25                 ` Bence Fábián
2015-07-25 11:31                   ` hiro
2015-07-24 17:09 ` Skip Tavakkolian

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=CAJDwFdj-KD9LuQm0pV-_AHZ9ciRw+rwRkyTQE1Q269uQg+kcNQ@mail.gmail.com \
    --to=prof.brucee@gmail.com \
    --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).