Pratique du Shadowing: Did Anthropic Kill Git? - Apprendre l'anglais à l'oral avec la vidéo

Choisissez un mode d'entraînement

Chaque mode ouvre une salle d'entraînement en plein écran.

65 phrases

Si les phrases sont trop courtes ou trop longues, cliquez sur Edit pour les ajuster.

Did Anthropic kill Git?

This week, a lot of people on X decided it did.

One post with over 600 ,000 views says Anthropic has replaced Git internally and the titans are falling.

Another says this is much bigger than it looks.

It all traces back to one post from Anthropic's own account, seen more than 6 .5 million times.

Part of the story is true.

Anthropic did stop using Git, but only for its own code, inside its own company.

Git itself is fine.

Anthropic keeps almost all of its code in one giant repository, a monorepo.

In May, about 2 ,500 changes were merged into it every day.

By September, it was over 30 ,000 a day.

On September 9th alone, 30 ,401 changes went in.

Their chart even has a dip in late July labeled the quiet week, and right after it, the line goes almost straight up.

Claude writes a lot of that code, and Anthropic says every bottleneck they remove leads to even more of it.

At that rate, the repository got heavy.

The history of the main branch alone is almost 100 gigabytes.

Their CI system checks out the code about 25 million times a day before you count developers, agent sandboxes, and research jobs.

Anthropic did the maths.

If every one of those checkouts fetched the repo the normal way, that would be over 600 petabytes of Git traffic every day.

Git was designed for a different kind of user.

Every clone is a full copy of the repository with all of its history, and it can do almost everything offline.

That's great for a person on a laptop on a plane.

At Anthropic, almost every client is an agent or a CI job, and those are always online.

They tried the usual fixes first, like shallow clones and sparse checkouts.

At the peak, they were running several hundred internal Git mirrors just to keep up.

So they built their own.

It's called Scion, and it moves the work from your machine to the server.

Commits, merges, rebases, blame, and history all happen on the server so there's nothing to push.

The client keeps a small cache and only downloads the files it actually reads.

A CI job that needs a diff can ask the server for it and never check out the code at all.

Between the client and the server sit two layers of caches, one on every machine and one in every region.

And each layer answers over 99 % of requests by itself.

Anthropic says it borrowed ideas from Google's Piper and Meta's Sapling, which were built for huge human teams.

On a developer machine, Git status took almost four seconds, and Scion does it in 19 milliseconds.

For agents, setting up a fresh work tree went from seven minutes to five seconds.

The whole system uses about 200 times less CPU and memory than the old mirrors, and CI got a quarter of its CPU back.

These are Anthropic's own measurements, and nobody outside the company has checked them yet seven people built it.

In five months, they made Scion, a code review tool called Antique, and a few other systems,

and they moved the whole monorepo over while the merge rate went up 10 times.

Claude wrote a lot of that code too.

The team had handwritten a pipeline to import the old Git history,

and an early version of Claude Mythos rewrote it to use 20 times less memory and run four times faster.

Every engineer on the project now rates Claude as better at writing code than they are.

They also say a big part of their job became telling Claude no

when it took shortcuts or piled on checks nobody needed.

On Hacker News, the thread passed 800 points and 900 comments in a day.

The most replied comment says that every time the writer stops reviewing Claude's code, they later find janky crap.

Others said a central server you always have to reach sounds a lot like subversion or perforce.

The older systems get replaced.

One person asked why Anthropic didn't just split up the monorepo.

On X, Dex Horthy pointed at the trade -off most people will feel.

Today, if GitHub is down, you can still commit on your laptop.

With Scion, if the server is down, you can't.

So did Anthropic kill Git?

No. In their own words, Scion is by no means a suitable replacement for Git for general use.

They say it only makes sense for truly enormous repos, with tens of thousands of engineers or swarms of agents.

It isn't open source and they don't plan to release it.

Your repos on GitHub don't change, and Claude code still works with plain Git.

A small team has already posted an unofficial open source version, but Anthropic has nothing to do with it.

What Anthropic wants is for Git to pick up some of these ideas,

like servers that do more of the work and answer questions about history through an API.

They say they want to build that with GitHub, GitLab, and the open source community,

and they expect other companies using AI coding tools to hit the same wall within a year.

If that happens, the changes will most likely land on the server side,

and the Git on your laptop will keep working the way it does today.

Télécharger l'application

Tout pour parler couramment

Prononciation IAChaque phrase notée

Phonétique (IPA)Maîtrisez chaque son

VocabulaireEnrichissez votre lexique

Jeu de vocabulaireApprenez en jouant

Scanner le QR

Download on theApp Store Get it onGoogle Play

FOR YOU

Vidéo recommandée

90 phrases

Vocabulaire et conseils d’expression pour cette leçon

Cette leçon d’expression orale s’appuie sur la vidéo « Did Anthropic Kill Git? ». Les mots qui reviennent le plus souvent : Git, Anthropic, code, server, Claude. Cette vidéo contient 65 phrases et 881 mots à répéter en shadowing. La partie parlée dure 4:49. Le locuteur parle vite, environ 183 mots par minute : attendez-vous à des liaisons et à des sons réduits. Seuls 79 % des mots font partie des 3 000 mots les plus courants en anglais, le vocabulaire est donc exigeant.

Vocabulaire clé de cette vidéo

15 mots de la vidéo à retenir, avec leur prononciation et leur sens :

Mot	Prononciation	Sens
server nom	/ˈsɝvɚ/	serveur
laptop nom	/ˈlæp.tɑp/	ordinateur portable, portable
merge verbe	/mɝd͡ʒ/	fusionner, amalgamer
mirror nom	/ˈmiɹɚ/	glace, miroir
layer nom	/ˈleɪ̯ɚ/	couche
commit verbe	/kəˈmɪt/	confier, commettre
developer nom	/dɪˈvɛləpɚ/	concepteur, développeur
clone nom	/kloʊn/	clone
checkout nom	/ˈt͡ʃɛkˌaʊt/	caisse
cache nom	/kæʃ/	cache, mémoire cache
chart nom	/t͡ʃɑɹt/	carte
replacement nom	/ɹɪˈpleɪsmənt/	remplaçant, substitut
thread nom	/ˈθɹɛd/	fil
label nom	/ˈleɪ.bəl/	étiquette, libellé
plain nom	/pleɪn/	plaine

Les verbes à particule que vous entendrez

Mot	Prononciation	Sens
check out verbe		mater, regarder
go up verbe		monter, s'élever
keep up verbe		maintenir, conserver
pick up verbe		soulever
set up verbe	/ˌsɛt ˈʌp/	mettre en place, installer

La grammaire de cette vidéo

Les structures que le locuteur utilise le plus, avec les mots exacts de la vidéo :

Structure	Dans la vidéo
Present perfect have/has + participe passé — une action passée qui compte encore maintenant	has replaced · has checked · has already posted
Voix passive be + participe passé — l’accent est mis sur ce qui arrive, pas sur qui le fait	were merged · was designed · were built

Prononciation à surveiller

Le locuteur utilise 5 contractions et formes réduites, comme don't, can't, didn't. Prononcez-les sous leur forme courte, telles que vous les entendez.

Les sons « th »: thread /ˈθɹɛd/, mathematics /mæθ(.ə)ˈmæt.ɪks/
Les sons « sh » et « zh »: cache /kæʃ/, measurement /ˈmɛʒ.ə.mənt/, shallow /ˈʃæloʊ/, unofficial /ʌn.əˈfɪʃ.əl/, shortcut /ˈʃɔːtkʌt/
Mots longs — placez bien l’accent: developer /dɪˈvɛləpɚ/, mathematics /mæθ(.ə)ˈmæt.ɪks/, internally /ɪnˈtɜːnəli/, unofficial /ʌn.əˈfɪʃ.əl/, repository /ɹɪˈpɒz.ɪ.t(ə.)ɹɪ/

Les sons difficiles pour les francophones :

/tʃ/ et /dʒ/ — à ne pas adoucir en « ch » et « j »: merge /mɝd͡ʒ/, checkout /ˈt͡ʃɛkˌaʊt/, chart /t͡ʃɑɹt/, fetch /fɛt͡ʃ/, janky /ˈd͡ʒæŋ.kiː/
/r/ anglais — langue recourbée, sans frotter la gorge: mirror /ˈmiɹɚ/, chart /t͡ʃɑɹt/, replacement /ɹɪˈpleɪsmənt/, thread /ˈθɹɛd/, trace /tɹeɪs/

Comment s’entraîner avec cette vidéo

Écoutez la vidéo en entier une fois sans parler et notez les mots que vous ne connaissez pas.
Commencez à la vitesse 0,75×, répétez phrase par phrase, puis revenez à la vitesse normale quand cela devient facile.
Enregistrez-vous et comparez avec l’original, en faisant attention à des mots comme server, laptop, merge.

Qu'est-ce que la technique du Shadowing ?

Le Shadowing est une technique d'apprentissage des langues fondée sur la science, développée à l'origine pour la formation des interprètes professionnels. Le principe est simple mais puissant : vous écoutez de l'anglais natif et le répétez immédiatement à voix haute — comme une ombre suivant le locuteur avec un décalage de 1 à 2 secondes. Les recherches montrent une amélioration significative de la précision de la prononciation, de l'intonation, du rythme, des liaisons, de la compréhension orale et de la fluidité.

Technique du shadowing : lire le guide complet étape par étape →

Pratique du Shadowing: Did Anthropic Kill Git? - Apprendre l'anglais à l'oral avec la vidéo

Choisissez un mode d'entraînement

Télécharger l'application

Did Google just dethrone OpenAI and Anthropic?

The easy way to keep your repos tidy.

How Did Ancient Humans Survive the Deadliest Predators on Earth?

The Philosophy of Rick Sanchez

The last real programmers are dying out...

Is React Native Dead? Shopify Is Leaving

Go’s Big Mistake

GitHub Copilot now controls your command line...

When AIs act emotional

We Let $200 GPT-Pro Think for 7 Days on Unsolved Math

Linus Torvalds Explains What Makes Linux So Fast

STOP Running Code On Your Computer