9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <charles.forsyth@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] troll paper
Date: Mon, 15 Apr 2024 21:50:52 +0100	[thread overview]
Message-ID: <CAOw7k5gZ68XC19iKQYRFD+teTrH6qWYNjewMnHh0xL7p0-owQw@mail.gmail.com> (raw)
In-Reply-To: <1B7C5BF9-844A-4488-82D5-63740AFE7E1B@westryn.net>

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

>
>  And, if I hear about it being
> “declarative” as a virtue, I point to the 81,000+ lines (and
> growing) of YAML, that I defy any one human to comprehend.


You might find help in culang.org

On Mon, 15 Apr 2024 at 20:49, Kim Shrier <kim@westryn.net> wrote:

> > On Apr 12, 2024, at 4:56 AM, David Arnold <davida@pobox.com> wrote:
> >
> >> The vetting process needs some work, lads.
> >
> > More heresy than trolling, perhaps?
> >
> > It was thought-provoking for me.  I wished I was there for the bar
> session afterwards.
> >
> > d
> 
> It didn’t read like a troll paper to me.  I periodically go through
> a similar exercise of thinking about how I would re-evaluate
> various Plan 9 decisions given the environment we find
> ourselves in, more than 35 years after the original work
> was done.
> 
> I do have an answer to the question, “Do we really have to
> have our own kernel?”.
> 
> Yes.
> 
> Making decisions about fundamental principles upon which
> you build your system has profound impacts on every aspect
> of the software, including the kernel itself.  Linux is not a good
> substitute for Plan 9.
> 
> And, I take particular exception to recommending Kubernetes
> as a tool for deploying services.  I am having to live through
> Kubernetes hell in my day job.  And, if I hear about it being
> “declarative” as a virtue, I point to the 81,000+ lines (and
> growing) of YAML, that I defy any one human to comprehend.
> 
> I do think it is a good exercise to reevaluate the premises on
> which one builds their systems in order to see if something
> needs to change or a completely different approach is
> warranted.
> 
> I just come to different conclusions than the author of this
> paper.
> 
> Kim
> _
> C++ is an off-by-one error
> 

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T51f7f5a8927e1271-Ma63b1c0f14990832dddeadef
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

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

  reply	other threads:[~2024-04-15 20:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-12 10:04 Anthony Martin
2024-04-12 10:25 ` Peter Hull
2024-04-12 10:56 ` David Arnold
2024-04-12 13:14   ` lists
2024-04-15 19:48   ` Kim Shrier
2024-04-15 20:50     ` Charles Forsyth [this message]
2024-04-15 21:11       ` michaelian ennis
2024-04-16  3:23       ` arnold
2024-04-16  3:29         ` Taj Khattra
2024-04-16  4:29           ` arnold
2024-04-16 14:11             ` Charles Forsyth
2024-04-16 14:17               ` ori
2024-04-16 14:24                 ` Charles Forsyth
2024-04-16 19:30                   ` G B via 9fans
2024-04-16 19:37                     ` Charles Forsyth
2024-04-16  4:08         ` Charles Forsyth
2024-04-16 14:21       ` Bakul Shah via 9fans
2024-04-12 13:12 ` lists
2024-04-12 13:28   ` Charles Forsyth
2024-04-14  5:42     ` michaelian ennis
2024-04-17 16:43 ` ron minnich
2024-04-19  9:17   ` Edouard Klein

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=CAOw7k5gZ68XC19iKQYRFD+teTrH6qWYNjewMnHh0xL7p0-owQw@mail.gmail.com \
    --to=charles.forsyth@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).