kyrra

hopefully it doesn't hurt. I've set it just incase.

Blaise Pascal: December 1656

"I have made this letter longer than usual, only because I have not had the time to make it shorter"

("Je n’ai fait celle-ci plus longue que parce que je n’ai pas eu le loisir de la faire plus courte").

> I find it difficult to get invested in Gemini because nobody will have access to Carbon for a few months anyways.

I feel like you're being overly dramatic here. Argon was 13 - 15 days.

Argon was announced September 30, made available on October 13 to Ultra everywhere, and Pro in the Gemini App. Pro plans got Argon on October 15 in AGY.

This is the first time they've slow-rolled a model. Who knows how long they'll wait on Carbon.

The Ultra-lite plans ($99/month) get some pretty good quota where you can actually use Argon some more. Maybe Google shouldn't be grouping together plans, but it should also be noted that $20/month also gets you 5TB of storage on Drive. If you paid for Dropbox, you get 3TB for $18/month (without any AI model usage).

(googler, opinions are my own)

Agents.md is a thing, you can ask it to not do that (it follows that ask pretty well).

Workspace always gets things slower than normal Gmail accounts. They do a lot more to isolate data related to those accounts, so that's likely the cause here.

Anytime anything gets added to Workspace, I think Google has a lot more contractual obligations about keeping it around for X amount of time, so they tend to be more careful about adding things.

As long as you know the use cases of your fields, renaming is just fine. My team regularly does it. We also maintain our own serializer and deserializer json, XML, and fixed with formats. The json one we handle serialization using an annotation to say how it should be exported.

Piper only works with CitC. Which is effectively a virtual file system when mounted locally. And when you have a monorepo that big, standard tools that want to scan an entire directory will stop working. Every part of the developer tool chain has to change to deal with code base that big.

I agree that Google should have bought github. The tech they built to scale Google Code I think would have helped a ton with GitHub.

It's really the case that Git is terrible at scale. Honestly most source control is.

When you have teams of 10,000+ people working on code, if you wanted to shard it, it will be lots of little projects, then you're going to have dependency hell. The core in for teams will either have to spend most of their time upgrading everyone's packages, our other teams are going to have to deal with those upgrades.

The core infra teams are either supporting lots of versions all at once, or spending extra time on source control.

I don't know about Uber, but at Google the monorepo is absolutely amazing.

I will the one big issues that is really hard in a monorepo, if you want to upgrade some external library not built by Google, when that library has a large breaking API change, it will never get upgraded.

Have those leads that left said why they left? Could it just be money?

My general take is all of The GPU design efforts are going toward Enterprise / datacenter graphics cards. They are just skipping a generation or two of consumer.