> We don't want or need hundreds of LLM generated Unix-clones which are merely slight variations on the Linux source code.

Good news, you don't have to use them. People want to build them, to learn, to explore, to feel good.

I'd argue that that's not even a good thing any more. It's borderline just drug use, and at the cost of huge amounts of energy.

Distillation does not require access to weights.

The page seems to be pretty clear that these are datacenters "owned and operated" by Google. They're not redefining "datacenter." The caches and edge PoPs are typically rented racks in partner datacenters, usually telcos and ISPs.

Selfies are used during live ID verification. (All of this is supposed to be encrypted, and destroyed within certain regulatory bounds.)

There is no perfect security. It's always flawed in some way.

Good security is extremely hard.

> because that's the definition of vibe coding.

That's _your_ definition of vibe coding.

That's the definition I am aware of, yes. It's also in the term, that you let a vibe (a force coming from the outside) decide what your work lead to, as opposed as to deciding where it should arrive at and leading into that direction.

> Karpathy described it as a form of coding where you "fully give in to the vibes, embrace exponentials, and forget that the code even exists"

If that's not "turning your brain off", what is?

What is your definition? Is there any difference between AI assisted development and vibe coding to you?