9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "G B via 9fans" <9fans@9fans.net>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] troll paper
Date: Tue, 16 Apr 2024 19:30:30 +0000 (UTC)	[thread overview]
Message-ID: <1086615499.10948377.1713295830132@mail.yahoo.com> (raw)
In-Reply-To: <CAOw7k5gr7M3KFFi4eP0zFnhodkwSkVTpKGuxBBR+qtnWur=LRw@mail.gmail.com>

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

 Isn't Cue YACL (Yet Another Configuration Language)? Absolutely no way one can deprecate YAML and just use Cue, so all one is doing essentially is adding one more thing to learn and keep updated. And since it hasn't released 1.0, what happens if the new YACL never materializes but was adopted? Good luck ripping that out to return to YAML.

    On Tuesday, April 16, 2024 at 09:26:28 AM CDT, Charles Forsyth <charles.forsyth@gmail.com> wrote:  
 
 Although cue itself is more generally useful, applied that way it's a coping mechanism that indeed doesn't address the fundamental point:like those Sendmail configuration languages that compiled down into the rewrite language instead of just replacing that.

On Tue, 16 Apr 2024 at 15:19, <ori@eigenstate.org> wrote:

Quoth Charles Forsyth <charles.forsyth@gmail.com>:
> 
> it's been a little while since i first looked at it, but i think one of the
> example application is exactly how one might use it to avoid 80k lines of
> yaml that you must look at directly.

while it may help -- this is just stacking complexity on top of
complexity.

kubernetes may be a tool that some of us need to deal with for
our jobs, but it has no place in a well designed rethink of the
world.


9fans / 9fans / seediscussions +participants +delivery optionsPermalink  
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T51f7f5a8927e1271-Me7b04f3e2f6e4c8db91448b5
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

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

  reply	other threads:[~2024-04-16 19:30 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
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 [this message]
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=1086615499.10948377.1713295830132@mail.yahoo.com \
    --to=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).