跟讀練習: The Rise Of Open-Source Software - 通過影片學習英語口語
選擇練習模式
每種模式都會開啟全屏練習室。
168 句
如果句子過短或過長,請點選 Edit 進行調整。
1
Much of the software that powers the world's largest companies, protects our personal data, or encrypts national security information is open to the public.
2
Anyone can download the source code behind Facebook's user interface, Google's Android operating system, or even
3
Goldman Sachs' data modeling program and use it as a building block for a totally new project.
4
What's more, lots of this software is actually developed collaboratively.
5
Created and maintained by an army of thousands, from unpaid volunteers to employees at competing tech companies.
6
As a kid in a small town in Virginia, I could get connected to the best developers anywhere on earth
7
and learn from them and even read the code that they'd written.
8
I really wanted to give back.
9
And these people were always my heroes.
10
So I wanted to participate too.
11
And my voice mattered.
12
It was just immediately I was hooked.
13
This is the collaborative world of open source software, where code is written and shared freely.
14
If individuals catch a bug or see an opportunity for improvement,
15
they can suggest changes to the code and thereby become a contributor to some of the biggest software projects on Earth.
16
But this model hasn't always been the norm.
17
At the dawn of the Internet era through the late 1990s, proprietary software proliferated.
18
Microsoft even went so far as to call open source un -American and bad for intellectual property rights.
19
Software was a finite commodity that people hoarded and wanted to sell as a product.
20
Open source software was only developed and maintained by a dedicated few.
21
And there was this fringe world,
22
there was this academic world who were creating software according to their own rules and sharing it publicly and making it free.
23
Certainly dreamed, like wouldn't it be awesome if we could sort of take over the world.
24
Now, open source has essentially taken over the world.
25
companies in every industry from Walmart to ExxonMobil to Verizon have open sourced their projects.
26
Microsoft has completely changed its point of view and is now seen as a leader in the space.
27
And in 2016, the U .S government even promised to open source at least 20 % of all its new custom -developed code.
28
So whether you know it or not, you are relying on volunteer labor in many cases of thousands of strangers from around the world.
29
In the 1970s, the MIT Artificial Intelligence Lab had a printer that regularly jammed.
30
So staff programmer Richard Stallman altered its source code so that when problems arose, it would send a message to everyone in the lab saying,
31
go fix the printer.
32
When the lab finally got a new printer, Stallman discovered its source code was inaccessible.
33
He asked for the code, got refused, got upset, and ultimately quit his job to develop a completely open operating system called GNU in 1983.
34
With this, Stallman spearheaded the free software movement from which the open source movement was born.
35
It's sort of a very natural way to work together.
36
Collectively, if everybody comes and contributes their piece,
37
you end up with something that's a lot greater than something that an individual could contribute on their own.
38
But throughout the 1980s and the 1990s, proprietary software still dominated.
39
And that was a very lucrative way of producing and selling software
40
and created an incentive for large technology companies to create a proprietary de facto standard.
41
It was against this backdrop that the open source operating system
42
Linux was unceremoniously released in 1991.
43
It incorporated many elements from Stallman's GNU project, but was mainly used by hobbyists looking for an alternative to Windows or Mac OS.
44
Throughout the decade, though, Linux gained momentum as large companies took advantage of its flexibility
45
and tweaked the software to their specific needs.
46
By the turn of the century, NASA, Dell, and IBM were all using it.
47
The platform itself changes nine times an hour.
48
10 ,000 lines of code are added to Linux every day.
49
About 5 ,000 lines are changed and about 8 ,000 lines are removed.
50
It is by far the highest velocity, most effective software development process in the history of computing.
51
As Linux grew, other open source projects were also gaining popularity, like the database management system MySQL, the Perl programming language, and the web server Apache.
52
But for the layperson at the turn of the century, the rise of these technologies could have gone unnoticed.
53
After all, hardly anyone ran
54
Linux on their personal computers.
55
But then, in 2008, Google released
56
Android devices, which run on a modified version of Linux.
57
Suddenly, the operating system blew up the smartphone market.
58
We are still overwhelmed with the amount of innovation that is happening in that ecosystem of Android.
59
Today there are over 2 .5 billion active devices using Android.
60
As Google demonstrated, businesses were increasingly relying upon this complex web of open source technologies to build products and platforms quickly.
61
And whether they knew it or not, this also meant that they were depending upon the vast open source community to maintain this software.
62
The ability for one company to produce the amount of software that's required for any modern technology product or service became overwhelming.
63
Today in a modern luxury automobile, there are more lines of software code than in an F -15 fighter jet.
64
There's just simply too much software to be written for any single organization to ride it themselves.
65
99 % of Fortune 500 companies use open source.
66
Every web server is pretty much Linux.
67
Most people choose to use open source programming languages.
68
It's this like amazing buffet.
69
You just come in and take this, this, this, this, this, and you slap together something.
70
You can build amazingly powerful products with very little work.
71
The sheer increase in volume drove a need amongst developers for a central repository where they could collaborate on these huge projects.
72
And in 2008, GitHub provided an answer.
73
What GitHub really did for open source is it kind of standardized the way
74
that people can contribute to open source projects and interface with them.
75
And so that any developer anywhere on earth knew how to contribute to a project on GitHub.
76
And that fed this explosion of open source activity.
77
Today, GitHub hosts the grand majority of the world's open source software projects.
78
And in 2018, Microsoft even acquired GitHub, affirming the tech giant's commitment to open source development.
79
We have about 140 million open source or software projects that are on GitHub,
80
and over 50 million of those have been added just in the last year.
81
So it's growing incredibly fast.
82
And the community has expanded far beyond idealistic hobbyists, as major companies are increasingly leading the charge, spearheading the development of open source projects in -house.
83
So we see companies like
84
Intel, Google, Facebook, Amazon, Microsoft, all contributing heavily to open source.
85
Googlers have been contributing to over 28 ,000 projects in 2018.
86
This number includes projects that Google has driven, as well as contributions it's made to projects led by other companies or individuals.
87
In the open source world, you have these fierce commercial rivals who collaborate every day together and they haven't signed anything.
88
And it's not just software companies.
89
ExxonMobil has open sourced its developer toolkit.
90
Walmart open sourced its cloud management platform.
91
And Goldman Sachs recently open sourced its data modeling program.
92
This open source way of working turned out to be better
93
because even in a big tech company where you might have 20 or 30 or 50 ,000 developers,
94
you can't compete with the 40 million developers that are now on GitHub working on open source every day.
95
Put simply, open source development has become the new norm.
96
And so I expect to see more and more investment into open source communities and more and more projects,
97
as well as companies finding ways to commercially monetize the activity that's collected across all of these different open source communities.
98
So how is open source monetized when the product is basically given away for free?
99
Basically, the answer lies in selling support services, subscriptions, and or commercial versions of the software.
100
Red Hat, founded in 1993, was the first to figure out a successful business model, which relies upon selling support services for its operating system,
101
Red Hat Enterprise Linux.
102
Anyone can download the software for free.
103
But if businesses want technical support and greater security, they'll need to buy a subscription.
104
After decades of commercial success, IBM officially acquired
105
Red Hat in 2019 for $34 billion.
106
It was the largest software acquisition in history.
107
It's really groundbreaking and it just shows the power and success of open source across the world, across the industries.
108
While Red Hat's 100 % open source model has been hard to replicate,
109
other companies like database program MongoDB and integration platform MuleSoft rely upon an open core model, meaning the basic features are free,
110
but add -ons and other useful elements are proprietary.
111
As these companies have racked up multi -billion dollar valuations, there's no doubt that on the enterprise level, there's big money in open source.
112
But as for the individual developers, the hobbyists who contribute to and maintain open source projects just for fun,
113
their path to profitability is much less clear.
114
There are a lot of different models for how people make money in open source.
115
One of the models is actually they don't.
116
A lot of them are volunteers and they do this in the free time, in the evenings and on the weekends.
117
But sometimes these just for fun side projects end up becoming widely used, critical to the internet infrastructure that we generally take for granted.
118
Certain projects get so popular and so widely used that, you know, they're in every product.
119
They're used by every company.
120
And then this result of like, you know, massive
121
Fortune 100, Fortune 500 companies building their businesses on top of this code that's written by hobbyists for who knows what reason, right?
122
As one might imagine, problems can arise
123
when critical systems are based on software
124
that's maintained by unpaid volunteers with no professional obligation to see to the maintenance of the project.
125
This issue came to a head in 2014.
126
When the security vulnerability dubbed Heartbleed was found in OpenSSL,
127
an open source encryption technology that's used by the majority of web servers to protect users' personal data.
128
The flaw has gone undetected for about two years and has exposed millions of usernames, passwords and possibly credit card info as well.
129
They left this lock capable of being picked because they didn't write the code quite right.
130
And when they looked into it, the OpenSSL team was tiny.
131
It was just a few people who were mostly working on donations and their donations had started to dry up.
132
And understandably, these incredibly talented programmers had a hard time justifying spending full time on this,
133
even though it was one of the most important building blocks of the entire Internet.
134
Ultimately, organizations like the Linux Foundation pulled together to provide financial support for OpenSSL, as well as other critical pieces of underfunded open source software.
135
But the disaster served as a wake -up call for an industry that still largely relies upon unpaid labor.
136
The burden on the maintainer can become quite intense.
137
You have sort of all these businesses coming in and saying, like, you know, your code is broken.
138
It's preventing me from getting my job done.
139
And so you get this, like, almost intense guilt.
140
I feel like a lot of maintainers have a guilt.
141
Now, companies are taking note and helping to formalize new funding models.
142
In 2019, GitHub rolled out their Sponsors program, which allows developers to give and receive recurring donations for their work.
143
We already have some people who are making their full living on GitHub Sponsors, so they don't have another job.
144
And so that's huge for us.
145
And that's really the key number that we are trying to move up.
146
For developers like Aboukadije, making a full -time living around open source is indeed the dream.
147
I prefer the freedom of being able to just follow my interests wherever they go
148
and solve whatever problems I think are interesting.
149
I'll never make money from some of the stuff I've worked on,
150
but I think I've done a lot of good in the world by working on it.
151
It's still early days, but if funding models like GitHub sponsors pay off,
152
we may see a new class of software engineers eschewing traditional tech jobs in favor of independent, open -source work.
153
Open -source has created so much technological progress, but because it never quite solved this funding problem in those early years,
154
I think that we are at a point now where we could lay the groundwork for the next stage of open source.
155
This could also mean expanding the cooperative ethos to industries outside of software.
156
As the idea of sharing technology and collaborating collectively expands,
157
we're moving into open hardware initiatives, data sharing initiatives.
158
And that's really going to be the future.
159
After all, the success of open source reveals that collaboration and knowledge sharing are more than just feel good buzzwords.
160
They're an effective business strategy.
161
And if we're going to solve some of the world's biggest problems, many believe that we can't afford to hoard our resources and learnings.
162
We have environmental concerns.
163
We're trying to understand things like cancer and Alzheimer's.
164
These are major collaborative efforts.
165
The complexity of building these technologies isn't going down.
166
It's only going up.
167
We can get that technology out there faster when everybody works together.
168
Thank you.
同頻道
FOR YOU
推薦影片
本課的詞彙與口語要點
這節口語課以影片“The Rise Of Open-Source Software”為素材。 影片中反覆出現的詞有:source, software, project, companies, code。 這段影片共有 95 個句子、2260 個單詞可供跟讀。 講話部分時長為 13:43。 說話人語速自然,每分鐘約 165 個詞,接近日常對話。 84% 的單詞屬於英語最常用的 3,000 詞,其餘的詞建議在練習前先學一下。
影片中的重點詞彙
影片中 15 個值得學習的單詞,附發音和釋義:
| 單詞 | 發音 | 釋義 |
|---|---|---|
| contribute 動詞 | /kənˈtɹɪb.jut/ | 貢獻 /貢獻 |
| rely 動詞 | /ɹɪˈlaɪ/ | 依賴 /依賴, 依靠 |
| volunteer 名詞 | /ˌvɑlənˈtɪɹ/ | 志願者 /志願者 |
| proprietary 形容詞 | /pɹəˈpɹaɪ.ə.tə.ɹi/ | 業主的 /業主的, 專賣的 /專賣的 |
| server 名詞 | /ˈsɝvɚ/ | 伺服器 /伺服器, 伺服器 |
| solve 動詞 | /sɒlv/ | 解決 /解決 |
| expand 動詞 | /ɪkˈspænd/ | 擴充套件 /擴充套件, 擴張 /擴張 |
| donation 名詞 | /doʊˈneɪʃən/ | 捐贈 /捐贈 |
| printer 名詞 | /ˈpɹɪntɚ/ | 印刷者 |
| unpaid 形容詞 | /ʌnˈpeɪd/ | 未付款的 |
| collaborate 動詞 | /kəˈlæb.ə.ɹeɪt/ | 合作, 協作 /協作 |
| compete 動詞 | /kəmˈpiːt/ | 競爭 /競爭, 高下 |
| enterprise 名詞 | /ˈɛntəˌpɹaɪz/ | 企業 /企業 |
| initiative 名詞 | /ɪˈnɪʃ.ə.tɪv/ | 主動權 /主動權 |
| database 名詞 | /ˈdeɪtəˌbeɪs/ | 資料庫 /資料庫 |
影片中出現的短語動詞
| 單詞 | 釋義 |
|---|---|
| take over 動詞 | 接管, 接手 |
| blow up 動詞 | 炸掉, 爆破 |
| end up 動詞 | 到達 |
| figure out 動詞 | 弄清楚 |
| give back 動詞 | 還 /還, 交還 /交還 |
| go down 動詞 | 下降, 下去 |
| go up 動詞 | 上昇 /上升, 上去 |
影片中的語法
說話人最常用的結構,並附上影片中的原話:
| 結構 | 影片中的用法 |
|---|---|
| 現在完成時 have/has + 過去分詞 — 過去發生但與現在仍有關聯的事 | hasn't always been · have been added · has expanded |
| 被動語態 be + 過去分詞 — 強調發生了什麼,而不是誰做的 | is actually developed · is written · was only developed |
| 定語從句 who / which + 從句 — 補充說明人或事物 | people who were · people who are |
需要注意的發音
說話人用了 20 次縮略和弱讀形式,例如 they're, we're, can't。請按聽到的簡短形式來說。
- “th” 音: thereby /ðɛɹˈbaɪ/, ethos /ˈiθɑs/
- “sh” 和 “zh” 音: donation /doʊˈneɪʃən/, initiative /ɪˈnɪʃ.ə.tɪv/, subscription /səbˈskɹɪpʃən/, essentially /ɪˈsɛnʃəli/, luxury /ˈlʌk.ʃə.ɹi/
- 長單詞——注意重音位置: developer /dɪˈvɛləpɚ/, proprietary /pɹəˈpɹaɪ.ə.tə.ɹi/, collaborate /kəˈlæb.ə.ɹeɪt/, incredibly /ɪŋˈkɹɛdɪbli/, initiative /ɪˈnɪʃ.ə.tɪv/
中文母語者容易讀錯的音:
- /v/ — 不要讀成 /w/,上齒輕觸下唇: developer /dɪˈvɛləpɚ/, volunteer /ˌvɑlənˈtɪɹ/, server /ˈsɝvɚ/, solve /sɒlv/, initiative /ɪˈnɪʃ.ə.tɪv/
- 詞尾子音 — 要讀清楚,後面不要加母音: contribute /kənˈtɹɪb.jut/, solve /sɒlv/, expand /ɪkˈspænd/, unpaid /ʌnˈpeɪd/, collaborate /kəˈlæb.ə.ɹeɪt/
- /r/ 和 /l/ 的區別: rely /ɹɪˈlaɪ/, volunteer /ˌvɑlənˈtɪɹ/, collaborate /kəˈlæb.ə.ɹeɪt/, incredibly /ɪŋˈkɹɛdɪbli/, collaborative /kəˈlæb.ə.ɹə.tɪv/
如何用這段影片練習
- 先完整聽一遍影片,不要開口,記下不認識的單詞。
- 先用 0.75 倍速逐句跟讀,熟練之後再回到正常速度。
- 錄下自己的聲音並與原聲對比,特別注意 contribute, rely, volunteer 這類單詞。
什麼是跟讀法?
跟讀法 (Shadowing) 是一種有科學依據的語言學習技巧,最初開發用於專業口譯員的培訓,並由多語言者Alexander Arguelles博士普及。這個方法簡單而強大:您在聽英語母語原聲的同時立即大聲重複——就像是一個延遲1-2秒緊跟說話者的影子。與被動聽力或語法練習不同,跟讀法強迫您的大腦和口腔肌肉同時處理並模模擬實的講話模式。研究表明它能顯著提高發音準確性,語調,節奏,連讀,聽力理解和口語流利度——使其成為雅思口語備考和真實英語交流最有效的方法之一。
































