跟讀練習: Did Anthropic Kill Git? - 通過影片學習英語口語
選擇練習模式
每種模式都會開啟全屏練習室。
65 句
如果句子過短或過長,請點選 Edit 進行調整。
1
Did Anthropic kill Git?
2
This week, a lot of people on X decided it did.
3
One post with over 600 ,000 views says Anthropic has replaced Git internally and the titans are falling.
4
Another says this is much bigger than it looks.
5
It all traces back to one post from Anthropic's own account, seen more than 6 .5 million times.
6
Part of the story is true.
7
Anthropic did stop using Git, but only for its own code, inside its own company.
8
Git itself is fine.
9
Anthropic keeps almost all of its code in one giant repository, a monorepo.
10
In May, about 2 ,500 changes were merged into it every day.
11
By September, it was over 30 ,000 a day.
12
On September 9th alone, 30 ,401 changes went in.
13
Their chart even has a dip in late July labeled the quiet week, and right after it, the line goes almost straight up.
14
Claude writes a lot of that code, and Anthropic says every bottleneck they remove leads to even more of it.
15
At that rate, the repository got heavy.
16
The history of the main branch alone is almost 100 gigabytes.
17
Their CI system checks out the code about 25 million times a day before you count developers, agent sandboxes, and research jobs.
18
Anthropic did the maths.
19
If every one of those checkouts fetched the repo the normal way, that would be over 600 petabytes of Git traffic every day.
20
Git was designed for a different kind of user.
21
Every clone is a full copy of the repository with all of its history, and it can do almost everything offline.
22
That's great for a person on a laptop on a plane.
23
At Anthropic, almost every client is an agent or a CI job, and those are always online.
24
They tried the usual fixes first, like shallow clones and sparse checkouts.
25
At the peak, they were running several hundred internal Git mirrors just to keep up.
26
So they built their own.
27
It's called Scion, and it moves the work from your machine to the server.
28
Commits, merges, rebases, blame, and history all happen on the server so there's nothing to push.
29
The client keeps a small cache and only downloads the files it actually reads.
30
A CI job that needs a diff can ask the server for it and never check out the code at all.
31
Between the client and the server sit two layers of caches, one on every machine and one in every region.
32
And each layer answers over 99 % of requests by itself.
33
Anthropic says it borrowed ideas from Google's Piper and Meta's Sapling, which were built for huge human teams.
34
On a developer machine, Git status took almost four seconds, and Scion does it in 19 milliseconds.
35
For agents, setting up a fresh work tree went from seven minutes to five seconds.
36
The whole system uses about 200 times less CPU and memory than the old mirrors, and CI got a quarter of its CPU back.
37
These are Anthropic's own measurements, and nobody outside the company has checked them yet seven people built it.
38
In five months, they made Scion, a code review tool called Antique, and a few other systems,
39
and they moved the whole monorepo over while the merge rate went up 10 times.
40
Claude wrote a lot of that code too.
41
The team had handwritten a pipeline to import the old Git history,
42
and an early version of Claude Mythos rewrote it to use 20 times less memory and run four times faster.
43
Every engineer on the project now rates Claude as better at writing code than they are.
44
They also say a big part of their job became telling Claude no
45
when it took shortcuts or piled on checks nobody needed.
46
On Hacker News, the thread passed 800 points and 900 comments in a day.
47
The most replied comment says that every time the writer stops reviewing Claude's code, they later find janky crap.
48
Others said a central server you always have to reach sounds a lot like subversion or perforce.
49
The older systems get replaced.
50
One person asked why Anthropic didn't just split up the monorepo.
51
On X, Dex Horthy pointed at the trade -off most people will feel.
52
Today, if GitHub is down, you can still commit on your laptop.
53
With Scion, if the server is down, you can't.
54
So did Anthropic kill Git?
55
No. In their own words, Scion is by no means a suitable replacement for Git for general use.
56
They say it only makes sense for truly enormous repos, with tens of thousands of engineers or swarms of agents.
57
It isn't open source and they don't plan to release it.
58
Your repos on GitHub don't change, and Claude code still works with plain Git.
59
A small team has already posted an unofficial open source version, but Anthropic has nothing to do with it.
60
What Anthropic wants is for Git to pick up some of these ideas,
61
like servers that do more of the work and answer questions about history through an API.
62
They say they want to build that with GitHub, GitLab, and the open source community,
63
and they expect other companies using AI coding tools to hit the same wall within a year.
64
If that happens, the changes will most likely land on the server side,
65
and the Git on your laptop will keep working the way it does today.
FOR YOU
推薦影片
本課的詞彙與口語要點
這節口語課以影片“Did Anthropic Kill Git?”為素材。 影片中反覆出現的詞有:Git, Anthropic, code, server, Claude。 這段影片共有 65 個句子、881 個單詞可供跟讀。 講話部分時長為 4:49。 說話人語速較快,每分鐘約 183 個詞,會出現較多連讀和弱讀。 只有 79% 的單詞屬於英語最常用的 3,000 詞,詞彙難度較高。
影片中的重點詞彙
影片中 15 個值得學習的單詞,附發音和釋義:
| 單詞 | 發音 | 釋義 |
|---|---|---|
| server 名詞 | /ˈsɝvɚ/ | 伺服器 /伺服器, 伺服器 |
| laptop 名詞 | /ˈlæp.tɑp/ | 手提電腦 /手提電腦, 手提計算機 /手提計算機 |
| merge 動詞 | /mɝd͡ʒ/ | 合併 |
| mirror 名詞 | /ˈmiɹɚ/ | җинзы, 鏡 /鏡 |
| layer 名詞 | /ˈleɪ̯ɚ/ | 層 /層 |
| clone 名詞 | /kloʊn/ | 克隆, 複製 /複製 |
| checkout 名詞 | /ˈt͡ʃɛkˌaʊt/ | 收款處 /收款處 |
| cache 名詞 | /kæʃ/ | 快取 /快取, 快取 |
| chart 名詞 | /t͡ʃɑɹt/ | 圖表 /圖表 |
| thread 名詞 | /ˈθɹɛd/ | 線 /線 |
| label 名詞 | /ˈleɪ.bəl/ | 標籤 /標籤, 簽條 /籤條 |
| plain 名詞 | /pleɪn/ | 平原, 平野 |
| suitable 形容詞 | [ˈsjuː.tə.bɫ̩] | 合適 /合適, 適當 /適當 |
| enormous 形容詞 | /ɪˈnɔː.məs/ | 巨大的 |
| trace 名詞 | /tɹeɪs/ | 痕跡 /痕跡 |
影片中出現的短語動詞
| 單詞 | 釋義 |
|---|---|
| check out 動詞 | 退房 |
| go up 動詞 | 上昇 /上升, 上去 |
| pick up 動詞 | 拾取, 撿 /撿 |
影片中的語法
說話人最常用的結構,並附上影片中的原話:
| 結構 | 影片中的用法 |
|---|---|
| 現在完成時 have/has + 過去分詞 — 過去發生但與現在仍有關聯的事 | has replaced · has checked · has already posted |
| 被動語態 be + 過去分詞 — 強調發生了什麼,而不是誰做的 | were merged · was designed · were built |
需要注意的發音
說話人用了 5 次縮略和弱讀形式,例如 don't, can't, didn't。請按聽到的簡短形式來說。
- “th” 音: thread /ˈθɹɛd/, mathematics /mæθ(.ə)ˈmæt.ɪks/
- “sh” 和 “zh” 音: cache /kæʃ/, measurement /ˈmɛʒ.ə.mənt/, shallow /ˈʃæloʊ/, unofficial /ʌn.əˈfɪʃ.əl/, shortcut /ˈʃɔːtkʌt/
- 長單詞——注意重音位置: developer /dɪˈvɛləpɚ/, mathematics /mæθ(.ə)ˈmæt.ɪks/, internally /ɪnˈtɜːnəli/, unofficial /ʌn.əˈfɪʃ.əl/, repository /ɹɪˈpɒz.ɪ.t(ə.)ɹɪ/
中文母語者容易讀錯的音:
- /v/ — 不要讀成 /w/,上齒輕觸下唇: server /ˈsɝvɚ/, developer /dɪˈvɛləpɚ/, subversion /sʌ̈bˈvɝ.ʒən/
- 詞尾子音 — 要讀清楚,後面不要加母音: laptop /ˈlæp.tɑp/, merge /mɝd͡ʒ/, commit /kəˈmɪt/, checkout /ˈt͡ʃɛkˌaʊt/, cache /kæʃ/
- /æ/ — 嘴張大,不要讀成 /e/: laptop /ˈlæp.tɑp/, cache /kæʃ/, mathematics /mæθ(.ə)ˈmæt.ɪks/, shallow /ˈʃæloʊ/, janky /ˈd͡ʒæŋ.kiː/
如何用這段影片練習
- 先完整聽一遍影片,不要開口,記下不認識的單詞。
- 先用 0.75 倍速逐句跟讀,熟練之後再回到正常速度。
- 錄下自己的聲音並與原聲對比,特別注意 server, laptop, merge 這類單詞。
什麼是跟讀法?
跟讀法 (Shadowing) 是一種有科學依據的語言學習技巧,最初開發用於專業口譯員的培訓,並由多語言者Alexander Arguelles博士普及。這個方法簡單而強大:您在聽英語母語原聲的同時立即大聲重複——就像是一個延遲1-2秒緊跟說話者的影子。與被動聽力或語法練習不同,跟讀法強迫您的大腦和口腔肌肉同時處理並模模擬實的講話模式。研究表明它能顯著提高發音準確性,語調,節奏,連讀,聽力理解和口語流利度——使其成為雅思口語備考和真實英語交流最有效的方法之一。












