シャドーイング練習: When open-sourcing your code goes wrong... - 動画で英語スピーキングを学ぶ
レッスンを作成中...
1
The programming world recently witnessed something unprecedented, the fastest rise of an open source project in the history of the universe.
2
A project that went from failed side project to over 200,000 GitHub stars in a matter of weeks.
3
A project that's already been acquired by OpenAI for probably some absurd amount of money.
4
That project, of course, is OpenClaw, a tool that's not much more than a basic JavaScript AI wrapper.
5
But what most people fail to realize is
6
that every piece of software you use today is built on the shoulders of giants.
7
And sadly, many of those giants died in battle a long time ago.
8
Nearly every piece of meaningful software out there is built with the blood, sweat, and tears of highly creative and talented programmers.
9
What's depressing, though, is that almost all of those programmers never got to reap the glory and money from their own creations.
10
In today's video, we're going to look at the stories of five open-source projects that achieved a meteoric rise, then crashed out under the weight of their own success.
11
It is February 26th, 2026, and you're watching The Code Report.
12
Yesterday, I was working on laying out some sick beats with the Arturia Microfreak.
13
But what I failed to realize is
14
that this commercial product is actually based upon the incredible work of the developer behind Mutable Instruments, Emily Gallay.
15
It's an incredible tool that can make sound waves do anything you can imagine.
16
It's coded by hand in C++, but there was always a problem in the background.
17
Burnout.
18
This project was managed by a solo business owner who just wanted something else in life.
19
And when she decided to move on to a new venture, the project simply faded away.
20
But as the old saying goes, it's better to burn out than to fade away.
21
And that's what happened to a popular project called Faker.js, a project that burned out in spectacular fashion.
22
Faker was a JavaScript library with millions of weekly downloads that generated fake data,
23
which was awesome for automated testing and astroturfing millions of fake users for your social media app to raise money from VCs.
24
But one fateful day in 2022, the developer Maroc Squires did something bold.
25
He deleted the source code, replaced it with the text Endgame, and published version 6.6.6 on NPM.
26
And this instabricked thousands of JavaScript apps when they went to update dependencies.
27
The corporations that depended on his work were rightfully pissed, but he was pissed himself for providing free work with no pay, and made this update in protest.
28
Unfortunately though, he was kicked out of his own project and it was taken over by a new developer, and still lives on today.
29
But sometimes, even projects that are well-funded with big teams can still fail, like Parse.
30
Before Supabase won, and even before Firebase won, there was a backend as a service called Parse in 2011 that provided a database and auth for mobile apps.
31
Developers loved it so much that Facebook acquired it for $85 million in 2013, which was considered a lot of money back then.
32
That gave the project access to the most talented developers in the industry, but just a few years later in 2016, it was killed by Facebook and shut down.
33
Any developer using it was forced to migrate to a new platform.
34
Zuck decided that hosting mobile app infrastructure was a waste of time, but this story has a semi-happy ending.
35
The code behind Parse Server was open-sourced, which allowed developers to self-host and maintain it independently.
36
But if you're an elderly developer from that time period, another project you might remember is Meteor, one of the first frameworks to do full-stack JavaScript before it was cool.
37
In 2013, Ruby on Rails was all the rage, but Meteor looked like the next big thing because it did all the same stuff,
38
but relied entirely on JavaScript instead of the beautiful yet esoteric Ruby language.
39
Its design also used WebSocket connections and stateful servers to perform instant UI updates that felt magical on early demos, but that was also part of the problem.
40
When apps went into production, they were difficult to maintain and didn't easily scale horizontally in the cloud.
41
When React and Angular hit the scene a few years later, devs decided it was best to separate the client from the server again, and its popularity slowly faded into the abyss.
42
Ironically, future frameworks like Next would start reintroducing these same concepts once again, but timing is everything in software, and Meteor was just born before its time.
43
Well, actually, maybe timing isn't everything, like in the case of Open Solaris.
44
In 2005, Linux was the dominant open-source operating system on servers,
45
But this superior new horse entered the race based on Sun Microsystems' Solaris Unix.
46
It has the ZFS file system, D-Trace observability, and even had containers before Docker was a thing.
47
On paper, it was the far better OS, but then in 2010, something really bad happened.
48
Oracle acquired Sun Microsystems, and almost overnight, the project's future evaporated.
49
Open development stopped, source releases quietly disappeared, and the community realized the experiment was over.
50
Oracle put Solaris back behind closed doors to protect its enterprise business, forcing developers to fork the last available code.
51
So even though the timing was great and it was technically brilliant, it failed because the ownership changed.
52
But possibly the most spectacular open source failure of all time is one you didn't see coming,
53
Mozilla Firefox, which is a prime example of when open sourcing your code goes wrong.
54
You see, in the 1990s, Netscape dominated the web browser market share, but Microsoft wanted a piece of that pie.
55
So what Microsoft did was bundle Internet Explorer directly into Windows, turning the browser into a free default instead of a product you had to choose.
56
When Netscape started losing market share, their response was radical.
57
Open sourced the browser and rallied the internet to its side.
58
The internet cheered, but the problem is that the code was a mess.
59
Eventually, this code became the Mozilla project, but the transition was a nightmare that required a near-total rewrite of all its legacy code.
60
Meanwhile, Internet Explorer rapidly captured new users through distribution alone.
61
By the time Mozilla eventually produced Firefox, which was faster, safer, and just better, Netscape itself was already dead.
62
The company lost the browser war, proving that open source can build better software, but it can't beat platform control and distribution.
63
Ironically, though, that same failure revived browser competition and laid the groundwork for the modern web, meaning Firefox succeeded technically by first losing commercially.
64
But if you dream of building your own failed open-source project in 2026, you need to know about CodeRabbit, the sponsor of today's video.
65
They just launched a new feature that lets you customize how their AI code reviewer writes pull request summaries.
66
So instead of wasting time decoding your team's PRs, you and your team can tell CodeRabbit exactly what information you want to see in every summary.
67
Like here, we made a doc telling it to include what changed and why, with special callouts to any branching changes or new dependencies.
68
CodeRabbit will follow these instructions to make sure that every PR gets a clean summary that everyone can quickly scan.
69
It's already saving dev teams hundreds of hours, and you can try it for free with the link below.
70
This has been The Code Report, thanks for watching, and I will see you in the next one.
📺 同じチャンネル
B21
10 very promising Open Source Projects you haven’t heard of
American Accent, en-USUniversity Students+2
C11
Array Map in 100 Seconds
American Accent, en-USUniversity Students+2
B21
7 Programming myths that waste your time
American Accent, en-USUniversity Students+2
C15
The plan to break apart Google... RIP Chrome
American Accent, en-USUniversity Students+3
C11
DHH has gone completely off the rails...
American Accent, en-USUniversity Students+2
C12
DNS Explained in 100 Seconds
American Accent, en-USUniversity Students+2
B23
Anthropic begged the world to stop AI… then shipped this
American Accent, en-USUniversity Students+2
B22
One man just liberated Fable... and now it’s illegal
American Accent, en-USUniversity Students+2
B22
7 Things No Programmer Ever Wants to Hear
American Accent, en-USBusiness English+1
B21
80% of programmers are NOT happy… why?
American Accent, en-USUniversity Students+2
C14
The most interesting hack in history just got weirder...
American Accent, en-USUniversity Students+2
B24
Raspberry Pi Explained in 100 Seconds
American Accent, en-USUniversity Students+2
C12
Did Google just kickstart the intelligence explosion?
American Accent, en-USUniversity Students+3
C13
Tragic mistake... Anthropic leaks Claude’s source code
American Accent, en-USUniversity Students+2
C1100+ Docker Concepts you Need to Know
American Accent, en-USUniversity Students+2
C129
Docker in 100 Seconds
American Accent, en-USUniversity Students+2
C13
The mystery is solved... and the answer is 40x cheaper than Claude
American Accent, en-USUniversity Students+2
B28
An ex-OpenAI researcher just deleted language from the LLM...
American Accent, en-USUniversity Students+2
B29
25 crazy software bugs explained
American Accent, en-USUniversity Students+2
B29
Git Explained in 100 Seconds
American Accent, en-USUniversity Students+2
✨ おすすめ動画
B21
276 文
Where did all the minimalists go?
American Accent, en-USUniversity Students+2
C11
85 文
AI Can Write Code. And That’s the Problem.
University StudentsBusiness English+1
C14
239 文
My 4.9-Star iOS App Is Actually a Website: Here’s How I Built It
University StudentsBusiness English+1
C11
270 文
Learning to code: How Pavel Durov learned to program | Lex Fridman Podcast Clips
University StudentsBusiness English+1
C12
542 文
The Future Of Work (& The New High-Income Skill Stack)
American Accent, en-USUniversity Students+2
C11
853 文
Why Coding Agents Keep Making Your Codebase Worse
University StudentsBusiness English+1
C11
345 文
What the heck is the event loop anyway? | Philip Roberts | JSConf EU
University StudentsBusiness English+1
B22
142 文
The Internet Didn't Fail. It Was Taken.
American Accent, en-USUniversity Students+3
C11
292 文
PirateSoftware is right, this needs to stop
University StudentsBusiness English+1
C11
108 文
How I Learned Procedural Generation
University StudentsBusiness English+1
この動画で英語スピーキング練習をする理由
テクノロジー関連の話題は、現代の英語コミュニケーションで頻出するため、シャドースピーチ（shadow speech）の題材として最適です。この動画では、オープンソースプロジェクトの盛衰を語る中で、専門用語や論理的な語順、感情を込めた発音が使われています。IELTSスピーキング対策にも役立つ、リアルなビジネス英語の雰囲気を体験できます。日常会話だけでなく、説明や議論のスキルを磨くのに最適なコンテンツです。
文脈の中の文法と表現
- 「built on the shoulders of giants」：比喩表現で「先人の功績に基づいて」という意味。技術関連の話でよく使われ、抽象的な概念を具体的に伝えるのに有効です。
- 「instabricked thousands of JavaScript apps」：「瞬時に壊した」というスラング的な表現。「brick」を動詞として使い、機械が使えなくなる様子を生き生きと表しています。
- 「timing is everything」：「タイミングが全て」という格言的なフレーズ。議論の結論として使われ、簡潔に要点をまとめるのに便利です。
発音の注意点
この動画の中には、発音が難しい単語やアクセントの変化があります。「meteoric」（流星のような）は「メテオリック」ではなく「ミーテオリック」と発音し、「esoteric」（難解な）は「エソテリック」ではなく「エソテリック」（アクセントが2番目の音節）です。また、「OpenClaw」「Parse」などの固有名詞は、原語の発音に近づけることが重要です。シャドーイングサイト（shadowing site）で繰り返し練習することで、自然な発音を身につけられます。
シャドーイングとは？英語上達に効果的な理由
シャドーイング（Shadowing）は、もともとプロの通訳者養成プログラムで開発された言語学習法で、多言語習得者として知られるDr. Alexander Arguelles によって広く普及されました。方法はシンプルですが非常に効果的：ネイティブスピーカーの英語を聞きながら、1〜2秒の遅延で声に出してすぐに繰り返す——まるで「影（shadow）」のように話者を追いかけます。文法ドリルや受動的なリスニングと異なり、シャドーイングは脳と口の筋肉が同時にリアルタイムで英語を処理・再現することを強制します。研究により、発音精度、抑揚、リズム、連音、リスニング力、そして会話の流暢さが大幅に向上することが確認されています。IELTSスピーキング対策や自然な英語コミュニケーションを目指す方に特におすすめです。