Not OP, but I kinda agree with them.

Teams are abstract, it’s easier to project your own ideals on to them. Not completely unlike respecting the office, even if loathing the politician currently holding it. It becomes “our thing”.

Also teams have longevity, or at least potential for longevity. Where I live, the two major local ice-hockey teams are founded in 1928 and 1967. There are families with generations of fans. Athlete’s career could be over in a decade.

So, a new not-a-markup-language, only human readable and editable, and objectively better than its predecessor? Well, it’s all according to tradition. I believe YAML got its start the same way.

YAML to JSON is probably doable, JSON back to YAML not so much.

There are multiple ways to mark multiline strings in YAML. Then there are anchors, like bionicjoey mentioned. Also comments, YAML has them. You’d have to have some way to retain the extra information, if you want to make the full round trip.

Here’s an example:

def-db: &def-db
    # here be dragons
    login: admin
    passwd: nimda
    
prod:
    db: *def-db
    desc: |
        I'm a teapot
        short and stout

dev:
    db: 
        <<: *def-db
        passwd: pass
    desc: "I'm a teapot\nshort and stout\n"

converted to JSON looks like this

{
    "def-db": {
        "login": "admin",
        "passwd": "nimda"
    },
    "prod": {
        "db": {
            "login": "admin",
            "passwd": "nimda"
        },
        "desc": "I'm a teapot\nshort and stout\n"
    },
    "dev": {
        "db": {
            "login": "admin",
            "passwd": "pass"
        },
        "desc": "I'm a teapot\nshort and stout\n"
    }
}

Yes, but no true Scotsman Christian…

I can’t even remember the last time I pirated a game.

I do. 2008, Sims 2. I owned a legit copy, but the DRM was too much of a hassle, plus I didn’t want my kids to scratch the discs. So I pirated a playable, child-proof version.

I almost got a bingo by checking off things I’ve muttered to myself.

The inverse is often true thanks to Linus’s Law.

The article you linked seems to suggest that Linus’s Law is a mere suggestion, at best.

No one is suggesting that open source is inherently less secure, just that the vulnerabilities are easier to find, and thus easier to get exploited. For a third party reviewer there’s a lot of incentive not to report bugs they would find in banking software.

If your software makes your clients’ life easier and your internal operations cheaper/faster/whatever, it’s a competitive advantage. Why would you give it away? Corporate greed or healthy competition, I suppose, depending on your point of view.

Distro developers were notified a month ago. At least Redhat and Debian have have published fixed versions. This is common procedure.

Objectively better

based on my personal opinion

I Still don’t care about cookies? From its description:

In most cases, the add-on just blocks or hides cookie related pop-ups. When it’s needed for the website to work properly, it will automatically accept the cookie policy for you (sometimes it will accept all and sometimes only necessary cookie categories, depending on what’s easier to do).

So, yeah, doesn’t accept everything, but might accept some.

Like I care. I’ve got a plugin that automatically accepts all cookies, and another one that deletes cookies when I leave the page.

Can’t remember the first airline proper, but my first flight was with a bush pilot. Old, well beaten floatplane, the first leg of our trip. Took a week to walk back, stopping to fish on every lake along the way.

Some new Debian users, usually coming from Ubuntu, are shocked by problems like “sudo not working in Debian”.

I didn’t need this earworm today.