I've got protonmail connected to a personal domain (in case I ever want to switch providers and keep my address), works fairly well.

Despite almost everything being in one big repo, it has silos. Not everyone has read access to everything. Some code, like the important bits of Search, is only available on a need-to-know basis.

So what happens if search adopts your internal library and your update to it breaks search? Do you need to get someone from the search team to go investigate? How is that prioritised?

The tooling is such that you will know if a change will break something in a silo before it is submitted. You then work with the affected team. It’s not a big deal.

it's search's fault for locking down their code and so search gets to fix it.

And if they don't think it's important right now? Are other teams who need the change just blocked?

? then their code doesn't build anymore and they will have a very sad time.

But I thought the precommit hooks would block this merge if it breaks search?

There’s no merge or precommit hooks or blocking.

If they chose to make their code invisible to me then I can’t fix it.

As the old saying goes, "’Tis impossible to be sure of any thing but Needing to Pee and Taxes."

That's an old YAML 1.1 behavior. It was removed in 1.2 (in 2009), though some implementations (looking at you, pyyaml) are still on 1.1.

Guess what was not removed?

    1 : 1,0
    2: 01
    3: 1.0
    4: 1O
    5: 0b1
    6: 0x1
    7: 0i1
    8: hey,
    8.0: oh,
    version: [3.1, "3.1", 3.10, "3.10"]

Gives you:

    {
    "1": "1,0", 
    "2": 1, 
    "3": 1.0, 
    "4": "1O", 
    "5": 1, 
    "6": 1, 
    "7": "0i1", 
    "8": "oh,", 
    "version": [
        3.1, 
        "3.1", 
        3.1, 
        "3.10"
    ]
    }

YAML turns raw literals into strings, except when the string matches a certain format. Then it may turn it into other things, like int or float, and you better know all the rules by heart and be attentive. And not introduce any typo, which of course no human ever does.

That's why yaml is a format for computer and json a format for humans

And that's also why everybody use JSON to configure CI, and use YAML for REST API.

So YAML is fine with breaking compatibility in minor version bumps?

Semver was not yet common practice when 1.2 was released.

https://yaml.org/spec/1.2.0/ says 2009

Not breaking backwards compatibility in a minor version bump of a data format was absolutely common sense in 2009.

semver.org -- which did an amazing job popularizing this idea -- did not yet have its webpage up in July 2009 (archive.org has it in December)

If you're worried about your data evaporating, consider using Google Inactive Account Manager to set up a way to automatically gift your data to a family member. https://support.google.com/accounts/answer/3036546?hl=en

We use the nanos heavily at my workplace. I've seen people make a chain out of paperclips when their nearest USB port is too far away (and they can't be bothered to grab an extension cable).

That's like asking "Why are people still manufacturing bikes, you'd think everyone who wants a bike would have one by this point". Bikes generally have shorter lifespans than people, and we're also making new people-who-want-bikes all the time.

I'm guessing that it's more like people are getting them stolen regularly. What I don't get is why the bottom of the pyramid (cf other branch of this thread) doesn't fill up.

Because people who possess stolen bikes are just as vulnerable to bike thrives as everyone else. If only non-stolen bikes got stolen, the pool of people willing to buy stolen bikes would probably not support any significant level of theft for very long, but that's.not how it works.

The government also can't stop you from robbing your neighbor, but that's not how laws work. Laws are about punishing you after the fact. If they catch you, of course.

It would be terrible to design it that way, but I think it's fine as a compiler optimization. Most of that datastructure is constant anyway, think of the memory savings!

Just imagine the sexually transmitted advertisements. Get a strange rash for a few days that has an ad for condoms printed on it.