쉐도잉 연습: The forgotten developer who saved JavaScript... - YouTube로 영어 말하기 배우기

B2
It's 2009.
⏸ 일시 정지
120 문장
문장이 너무 짧거나 길면 Edit를 눌러 조정하세요.
1
It's 2009.
2
You're at a Hannah Montana movie,
3
and your phone won't stop buzzing with notifications from a new dating app you just downloaded.
4
Your favorite artist is supposed to be releasing a new album next year.
5
Your favorite TV show is currently being made into a movie.
6
And you're still riding high from arguing how many days are in a week on the bodybuilding.com forums.
7
Life is good, at least on the weekends.
8
Because during the week, you have to spend all day using the worst programming language ever invented.
9
A language that was famously designed in 10 days,
10
but after using it, it had you wondering what Brendan did after day two.
11
A language that every browser interpreted differently,
12
had no standard library, modules,
13
or classes, and if your primary job was to write it,
14
I'm told you were a massive loser who didn't deserve to feel love.
15
At least that's how things were in 2009.
16
But over the next decade, that sentiment changed.
17
JavaScript went from being a language that you'd never touch directly without putting on a jQuery hazmat suit first,
18
to arguably the most popular programming language in the world,
19
while JavaScript developers, despite all the stupid stickers on their MacBooks,
20
went from being considered script kitties to real programmers with actual feelings and emotions.
21
So how exactly did this mass psychosis happen?
22
There's a bunch of different reasons,
23
but in my opinion,
24
I think the most underrated was all led by a single person who has since been forgotten to time, Jeremy Ashkenis.
25
In 2009, Jeremy was a developer at Document Cloud,
26
where he had the unfortunate task of working on a heavy client-side JavaScript application,
27
which was rare at that time.
28
Having a background in Ruby,
29
but being forced to write JavaScript,
30
I assume every morning he'd wake up and think to himself,
31
wow, today might be a good day to b***ing b*** myself off the b***ing Golden Gate Bridge.
32
But unlike everyone else who had JavaScript Stockholm Syndrome,
33
Jeremy had the audacity to think he could fix it,
34
and so he did.
35
His first act was dealing with the fact that JavaScript had no standard library.
36
Again, this was 2009.
37
Although Firefox had shipped support for some array helper methods like map,
38
reduce, and foreach, Internet Explorer hadn't yet,
39
which meant you couldn't use them unless you polyfilled them.
40
So to fix this, Jeremy released Underscore.js,
41
a utility belt library that contained about 60 helper functions that made it easier to work with the Rays and Objects.
42
Now, I know that doesn't sound exciting today,
43
but building for the web was so bad back then
44
that Underscore likely did save a few people from throwing themselves off the f***ing Golden Gate Bridge.
45
Underscore got so popular that many of its features were adopted into the JavaScript language itself,
46
which eventually made it obsolete.
47
But Underscore was only Jeremy's first act.
48
Next, he decided instead of augmenting fish head JavaScript with a new library,
49
he'd have more freedom if he just created an entirely new language with large cannons.
50
Again, I can't stress this enough,
51
the JavaScript in 2009 was very different than it is today.
52
There were no classes,
53
so inheritance was done through a pattern where you'd manually attach properties to a hidden object called prototype
54
that every function had access to.
55
The only way to declare a variable had bizarre scoping rules that hoisted declarations to the top of a function,
56
whether you were aware of it or not.
57
No one really understood or cared about the difference between the equality operator and the identity operator,
58
so you'd have a bunch of type coercion happening without even realizing it.
59
And to define even a simple function,
60
you had to literally type out the word function every single time,
61
which led to some pretty ugly code.
62
By building a new language that compiled a JavaScript,
63
Jeremy could fix it without having to wait for the standards committee or browser vendors to do it themselves.
64
And even better, he could leave JavaScript the bad parts in that musty room Brendan spent 10 days in.
65
And for a while, CoffeeScript was huge.
66
Father DHH adopted it almost overnight,
67
and in 2011, it shipped as the default JavaScript preprocessor in Rails 3.1,
68
meaning the front end for every new Rails app in the world was suddenly written in CoffeeScript.
69
GitHub, Dropbox, and a long list of early 2010 startups adopted it,
70
and for a few years,
71
it was the default choice for anyone who took JavaScript seriously.
72
Today, CoffeeScript is basically dead after its best features were absorbed into JavaScript itself,
73
but every time your agent writes a class,
74
arrow function, default parameters, a spread operator,
75
does string interpolation, or destructures a value, you can thank CoffeeScript.
76
But Jeremy still wasn't done yet.
77
By 2010, he had given JavaScript a standard library with underscore,
78
and a better syntax with CoffeeScript.
79
But there was still one massive problem left.
80
There was no good way to actually structure a JavaScript application.
81
If you wanted to build a large,
82
client-side-heavy app, you would still end up with thousands of lines of spaghetti where your data,
83
DOM manipulation, and event handlers were all tangled together.
84
So in 2010, Jeremy released Backbone.js,
85
a tiny library of less than 2,000 lines of code
86
that gave JavaScript developers their first real taste of MVC on the front end.
87
It introduced models for your data,
88
collections for groups of models,
89
views for rendering, and an event system that let everything stay in sync without the need to wire it up by hand.
90
But for the first time,
91
you could build a serious client-side app without it collapsing under its own weight.
92
And with Jeremy's track record,
93
it quickly caught on, powering the early versions of Trello,
94
Airbnb, Hulu, Pinterest, and basically every other startup that needed a real front end between 2011 and 2014.
95
If you were a JavaScript developer during that window,
96
you almost certainly wrote Backbone,
97
and you probably thought it was the future.
98
But as it turns out, it wasn't.
99
Angular, Ember, and eventually React would make Backbone obsolete by taking its core ideas and pushing them further.
100
But Backbone was the library that proved you could actually build client-side heavy applications.
101
It's easy to forget how bad JavaScript used to be,
102
and even easier to forget the people who fixed it.
103
But the modern web was built on top of ideas that Jeremy Ashkenis pioneered,
104
even if no one remembers him.
105
But speaking of things you no longer have to build yourself,
106
Auth is another one, thanks to Clerc,
107
the sponsor of today's video.
108
They just launched the Clerc CLI,
109
which comes with commands that are even more powerful than the ones I saw at that human dog show.
110
Just run clerk init in any directory,
111
and it'll set up end-to-end authentication for your entire project with custom middleware,
112
auth pages, and environment variables.
113
It even detects if you're migrating from next auth or auth zero and walks you through the entire process.
114
And since they know you're using agents to do all your dirty work,
115
they also created clerk skills,
116
which ships framework-specific patterns pinned to the CLI version so your coding agent knows exactly how to use it.
117
And the clerk API command lets your agent hit the entire clerk backend API from the terminal without copy and pasting credentials.
118
Try it out for free today at the link below,
119
or just run clerk init to get started.
120
Thanks for watching, and I will see you in the next one.

앱 다운로드

당신이 말하는 모든 문장을 AI가 채점

스캔하여 다운로드
스캔하여 다운로드
Download on theApp Store
Get it onGoogle Play
TRENDING

인기 동영상

맥락 및 배경

이 비디오는 JavaScript의 역사를 돌아보고, 잊혀진 개발자인 제레미 아쉬케니스(Jeremy Ashkenis)가 어떻게 이 언어를 변화시켰는지를 다루고 있습니다. 2009년, 많은 개발자들은 JavaScript에 대한 부정적인 인식을 가지고 있었고, 이는 사용을 더욱 어렵게 만들었습니다. 하지만 제레미는 그 상황을 개선할 수 있다고 믿었고, 그의 노력으로 JavaScript는 가장 인기 있는 프로그래밍 언어로 성장하게 됩니다. 이러한 배경 속에서 비디오 내용 및 주요 용어를 통해 영어 회화를 연습할 수 있는 기회를 제공합니다.

일상 커뮤니케이션을 위한 5가지 주요 표현

  • It's 2009. - 2009년이었습니다.
  • Life is good, at least on the weekends. - 인생은 좋습니다, 적어도 주말에는요.
  • JavaScript had no standard library. - JavaScript에는 표준 라이브러리가 없었습니다.
  • Having a background in Ruby. - 루비 배경이 있습니다.
  • He had the audacity to think he could fix it. - 그는 이를 고칠 수 있을 거라고 생각할 용기가 있었습니다.

단계별 섀도우잉 가이드

이 비디오의 내용을 효과적으로 섀도우 스피크(shadow speak)하기 위해 다음 단계를 따라 해보세요. 이는 영어 회화 연습에 매우 유용합니다.

  1. 비디오 시청: 처음에는 비디오를 전체적으로 시청하며 내용을 이해하세요.
  2. 구문 반복: 각 문장들을 들으면서 따라 말해보세요. 특히, 위의 5가지 표현에 집중하세요.
  3. 부분 반주: 비디오의 특정 부분을 반복 재생하고, 문장을 하나씩 따라하는 연습을 합니다. 발음과 억양에 주의하세요.
  4. 자연스럽게 말하기: 문장들을 익힌 후, 자신의 말로 이 내용을 설명해 보세요. 이를 통해 자주 사용하는 문장을 자연스럽게 만들어 갈 수 있습니다.
  5. 피드백 받기: 친구나 선생님에게 발음이나 표현에 대해 피드백을 받아보세요. 이를 통해 개선점을 찾아보세요.

이 과정을 통해 유튜브 영어 공부와 섀도우 스피치(shadow speech)에 있어 더욱 능숙해질 수 있습니다. 지속적으로 연습하며 흥미로운 내용을 통해 영어 회화 능력을 발전시켜 보세요!

쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법

쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.

☕ 커피 한 잔 사주기