News for hackers. Stuff that matters.
Re:The CUE Data Constraint Language by svnpenn on Friday July 05, 2019 @04:13PM (#20365482)
I just cant understand how a sane person would use syntax like this:

    { home       = "/home/bill"
    , privateKey = "/home/bill/id_ed25519"
    , publicKey  = "/home/blil/id_ed25519.pub"
    }
and call it "human friendly" with a straight face. just use the normal syntax:

    {
       home = "/home/bill",
       privateKey = "/home/bill/id_ed25519",
       publicKey  = "/home/blil/id_ed25519.pub"
    }
advocates will say, "well you can delete the last line without it breaking". ok. but what about the first line? youve just moved the problem. its frustrating because this is a solved problem. either remove comma altogether (YAML) or allow trailing comma (Python). Dont do this weird leading comma stuff. Its just living in denial.
Re:The CUE Data Constraint Language by swsieber on Friday July 05, 2019 @06:16PM (#20366323)
Hmm... the advocates I've run into say that you can add a newline with out modifying the old last line. And that one makes sense, since you tend to (or at least I tend to) add things at the end.
Re:The CUE Data Constraint Language by saagarjha on Friday July 05, 2019 @06:45PM (#20366486)
That's why every well-designed language lets you put an extra commas on the last line.
Re:The CUE Data Constraint Language by throwawayjava on Friday July 05, 2019 @07:20PM (#20366683)
Really? They seem equally readable to me.

I can't tell why a sane person would care much one way or the other, other than the way sane people care about vim vs emacs or tabs vs spaces or Kirk vs Picard...