쉐도잉 연습: Does Anyone Use JavaScript Anymore? - 영상으로 영어 말하기 배우기
레슨 만드는 중...
1
Hey, what's going on guys?
2
So I built most of my career teaching JavaScript, whether it was Vanilla, Node.js, React, the Mernstack, all the way back to,
3
you know, jQuery and frameworks like Knockout and AngularJS.
4
But if you open up any of my current projects, you're probably not going to see many JS or JSX files.
5
TypeScript has definitely become the default for most of the web projects I work on now.
6
And it definitely isn't just me.
7
In the, I guess, the framework heavy part of the web world, TypeScript is absolutely everywhere.
8
So I've been asked the question, does anyone even use JavaScript anymore?
9
And that's what I kind of want to unpack in this video is how much has the ecosystem actually shifted toward TypeScript?
10
Why has it become the default for so many projects?
11
Should beginners still learn JavaScript first?
12
And where does plain JavaScript still make more sense?
13
All right, so before we jump in, I just want to mention today's sponsor, CodeRabbit.
14
So you know how when you open up a pull request, you get a list of files in alphabetical order, and that's it.
15
That's your context.
16
So you're basically reconstructing what the PR does file by file.
17
And CodeRabbit builds something called ChangeStack, and it fixes that.
18
So you start on an overview page, you get a summary, a walkthrough, all the reviews and comments in one place.
19
And if it's a merge conflict or CI's failing, there's a blocker section where you can fix it in one click.
20
So your changes get grouped into layers and cohorts, so related stuff sits together instead of being alphabetized.
21
And there's also a timeline view which shows you why things changed and not just what,
22
and a semantic diff so when you move a big block of code it doesn't show up as 200 deletions and additions.
23
You see the actual change.
24
So links in description, check out CodeRabbit if you're interested.
25
Okay, so I'll save you the suspense.
26
Obviously, no, JavaScript is not dead.
27
It runs pretty much the entire interactive web, so this isn't one of those overly dramatic JavaScript is finished videos.
28
At the end of the day, TypeScript's type information is removed, and the code that actually runs is JavaScript,
29
and TypeScript has become kind of the popular way to author JavaScript, but there has been a real shift,
30
and it's how much of the JavaScript ecosystem now assumes that you're going to be using TypeScript.
31
So before anything, I just want to look at the data.
32
I don't want to just go on my own experience.
33
So according to GitHub's 2025 Octoverse report,
34
TypeScript became the number one language on GitHub based on monthly contributors passing both Python and JavaScript.
35
And in the 2025 State of JavaScript survey,
36
it found that respondents spent 77% of their JavaScript and TypeScript coding time writing TypeScript.
37
And I expect that to be even bigger in this year's survey.
38
Now that doesn't mean that TypeScript has replaced JavaScript.
39
GitHub actually still saw more new JavaScript repositories altogether, but the trend is pretty clear.
40
TypeScript has become a very common choice for modern application development.
41
Now, I want to look at where we're seeing TypeScript more and more.
42
So we'll start with the front end.
43
So obviously, you know, React has full TypeScript support.
44
Vue is written in TypeScript, has first class support for it.
45
Angular components are TypeScript classes, even though that's been the case since Angular 2 was released.
46
And you can still use regular JavaScript or write regular JavaScript with React or Vue,
47
but when you spin up a new app using Vite or another CLI, you're most likely going to be getting TS and TSX files.
48
Then you move to the backend.
49
So Node can now run TypeScript files directly.
50
It strips out the types and runs JavaScript underneath.
51
This gets even more useful when the front end
52
and backend live in the same monorepo because you might have a web app, an API, a background worker, maybe a shared package.
53
And instead of defining a user or product or API response in three different places, you define it once, you import it wherever you need it.
54
And that ability to share types without duplicating them is a huge part of the appeal of full stack TypeScript.
55
You also have Zod, which is a very popular TypeScript validation library
56
that takes that idea even further because you can define a schema once, infer the TypeScript from it,
57
and use that same schema to validate real data at runtime.
58
And TypeScript has also moved well beyond traditional web apps.
59
You have new React Native projects using TypeScript as default for mobile apps.
60
You have Electron has TypeScript templates for desktop apps.
61
And now in the age of AI, TypeScript has only gotten bigger.
62
And I'm not saying that all AI development is TypeScript.
63
Obviously, you have Python is massive in AI and machine learning, but the application layer around AI has a ton of TypeScript.
64
You have Vercel's AI SDK, which describes itself as a TypeScript toolkit.
65
Even if you go and prompt Clot or Codex right now to create a React app, it's most likely going to be using TypeScript.
66
So when you take a step back and you look at all those things together, it's much bigger than developers just wanting red squiggly lines in their editor.
67
You know, TypeScript has become a common language across a huge part of the application stack.
68
So bottom line, it's everywhere.
69
Now, I do want to talk a little bit about why.
70
I think that the benefits matter because this level of adoption, it didn't just happen for no reason.
71
So one reason TypeScript caught on is that it brought ideas that had been common in other languages into the JavaScript world.
72
And I became a developer over 15 years ago, closer to 20 at this point, which makes me feel very old.
73
But I remember people saying that JavaScript was like a toy language.
74
And this was before Node.js, before modern front-end frameworks and all the tooling we have now.
75
And back then, JavaScript was mostly seen as like a little scripting language for things like form validation and drop downs.
76
And if you came from Java, C Sharp, C++, JavaScript, it felt really just loose and a bit chaotic.
77
And those languages already had static types and interfaces, generics, compile time checks.
78
And TypeScript brought some of that familiar structure into the JavaScript ecosystem.
79
And I also think it gave JavaScript a bit more street cred, or I guess nerd cred.
80
And I would say that the practical benefits of TypeScript are what make it stick.
81
And, you know, things like if you rename a variable to, let's say, from name to full name on a shared user type, TypeScript can immediately show you every component,
82
every API route or function that's still looking for that name variable.
83
And autocomplete is more accurate.
84
You can see, you know, what a function expects, jump to its definition
85
and rename something across an entire project with much more confidence than you could before.
86
And types become contracts that help explain how different pieces are supposed to fit together.
87
So your code is just much more verbose and just defined better.
88
And I was pretty much against TypeScript for a long time and people would give me shit for it online.
89
And one of my biggest gripes back then was that it felt like a lot of extra setup, but now frameworks, libraries, build tools, they all support it extremely well.
90
And it's even the default for most of them now.
91
TypeScript's inference has also gotten much better over the years.
92
So you can often get strong type checking without manually annotating everything.
93
So even if you don't want to write a ton of TypeScript syntax, you can still get better type checking,
94
autocomplete, safer refactoring, and really not do anything.
95
So there's really not a reason not to use it anymore.
96
And a lot of our code is now written with AI, and the types give us just one more feedback loop.
97
Using it with AI definitely doesn't make the generated code correct, and agent can still write perfectly typed garbage.
98
It should never replace tests or code review.
99
It's just one more useful layer of feedback.
100
So now the question, should beginners learn JavaScript?
101
Absolutely.
102
If you're learning web development, I would not skip JavaScript and jump directly into memorizing TypeScript syntax.
103
I would learn all you can or all you should about JavaScript first.
104
Obviously, functions, objects, arrays, scope, asynchronous JavaScript, the DOM, of course,
105
and just how the language behaves at runtime before you throw anything else on top of it.
106
And when something weird happens in a TypeScript application, it's usually your JavaScript knowledge that helps you understand why.
107
But once you learn those fundamentals, TypeScript should be one of the next steps.
108
If you want to build, you know, modern applications or work on a development team, and you don't need to become a type system wizard,
109
just learn the types you'll see in real projects and learn how to read the errors.
110
Now
111
that jump from I know JavaScript to I can work comfortably
112
in a TypeScript code base is exactly why my team and I built TypeScript fundamentals on start.dev, which is our new interactive learning platform.
113
And it's built around learning by doing instead of sitting in front of another long lecture or video.
114
So basically you write code directly in the browser and your work is checked as you go.
115
Not only that, but you have AI Brad.
116
He has full context of each lesson.
117
He can see your code and you can ask him questions when you get stuck.
118
So basically you get AI version of me helping you along the way and students have been loving it.
119
So if TypeScript is next on your list, then check out TypeScript fundamentals through the link in the description.
120
And it's free to start completely free.
121
And there's also a 20% discount for the premium membership in the description.
122
And if you already know TypeScript and you want to take, take, you know, take to the next step, we also have a validation with Zod course as well.
123
Now, none of this means every project suddenly needs TypeScript, I still use plain JavaScript when it fits the job.
124
So for, you know, a small script, a quick prototype or a simple project with very little code, TypeScript may add more friction than value.
125
So sometimes you just want to create a file, write a few lines of JavaScript and run it.
126
Plain JavaScript also makes sense when you're teaching the fundamentals, obviously.
127
You know, if the point is to understand functions, the DOM, HTTP, Node.js, or how the language behaves at runtime,
128
adding a type system can just become another thing to kind of cloud that other stuff.
129
Sometimes the simplest tool is the right tool.
130
And choosing JavaScript doesn't mean somebody is an amateur.
131
It means they made a trade-off.
132
You know, TypeScript adds value, but it also adds concepts, configuration, and another category of errors that developers have to understand.
133
So to answer, does anyone even use JavaScript anymore?
134
Of course, JavaScript still powers the web and TypeScript depends on it.
135
But look at the front end, back end, monorepos, mobile apps, desktop apps, developer tooling, and the application layer around AI.
136
TypeScript is now a normal part of all of that.
137
And that doesn't mean TypeScript replace JavaScript, it just means a huge part of the ecosystem has standardized on a typed way to write it.
138
And it doesn't mean every project needs TypeScript or that beginner should skip JavaScript, learn JavaScript, understand the foundation,
139
and then add TypeScript when the project earns it.
📺 같은 채널
✨ 추천 영상
B22
185 문장
Use these CSS features instead of JavaScript
Business EnglishUniversity StudentsWorking Adults
C13
78 문장
Tragic mistake... Anthropic leaks Claude’s source code
American AccentBusiness EnglishUniversity StudentsWorking Adults
B21
12 문장
How I’d Learn Coding in 2026 (Without Wasting Years)
Business EnglishUniversity StudentsWorking Adults
C11
132 문장
Video
Business EnglishUniversity StudentsWorking Adults
C11
218 문장
Next.js 16.3 got good (if you care)
Business EnglishUniversity StudentsWorking Adults
C11
333 문장
Master n8n Triggers in 20 Minutes – Automate Anything
Business EnglishUniversity StudentsWorking Adults
C12
195 문장
JavaScript Visualized - Event Loop, Web APIs, (Micro)task Queue
Business EnglishUniversity StudentsWorking Adults
C11
54 문장
Traceroute: You're Probably Reading the Results Wrong
Business EnglishUniversity StudentsWorking Adults
C13
173 문장
STOP Running Code On Your Computer
Business EnglishUniversity StudentsWorking Adults
B21
202 문장
Is React Native Dead? Shopify Is Leaving
Business EnglishUniversity StudentsWorking Adults
C13
33 문장
TypeScript in 100 Seconds
American AccentBusiness EnglishUniversity StudentsWorking Adults
B21
64 문장
JTBD Framework in UX w/ Examples | UXtweak
Business EnglishUniversity StudentsWorking Adults
이 레슨의 어휘와 말하기 포인트
이 C1 수준 말하기 레슨은 영상 “Does Anyone Use JavaScript Anymore?”을(를) 바탕으로 합니다. 가장 자주 반복되는 단어는 다음과 같습니다: Typescript, Javascript, type, code, project. 이 영상에는 섀도잉할 문장 139개와 단어 1992개가 있습니다. 말하는 구간의 길이는 11:53입니다. 화자는 분당 약 168단어로, 일상 대화에 가까운 자연스러운 속도로 말합니다. 영어에서 가장 많이 쓰이는 3,000단어에 속하는 단어가 78%뿐이라 어휘가 어려운 편입니다.
이 영상의 핵심 어휘
영상에서 가장 어려운 단어 15개를 발음, 뜻과 함께 정리했습니다.
| 단어 | 발음 | 뜻 |
|---|---|---|
| ecosystem 명사 | /ˈikoʊˌsɪstəm/ | 생태계 |
| beginner 명사 | /bəˈɡɪnɚ/ | 초심자, 초보자 |
| rename 동사 | /ɹiːˈneɪm/ | 개명하다 |
| schema 명사 | /ˈskiːmə/ | 스키마 |
| syntax 명사 | /ˈsɪn.tæks/ | 통어론, 구문론 |
| desktop 명사 | /ˈdɛsktɒp/ | 탁상 |
| behave 동사 | /bɪˈheɪv/ | 처신하다, 행동하다 |
| stack 명사 | /stæk/ | 무더기 |
| interactive 형용사 | /ˌɪn.tɚˈæk.tɪv/ | 인터랙티브 |
| alphabetical 형용사 | /ˌæl.fəˈbɛt.ɪ.kəl/ | 알파벳의 |
| deletion 명사 | /dɪˈliːʃən/ | 삭제 |
| memorize 동사 | /ˈmɛm.əˌɹaɪ̯z/ | 기억하다, 암기하다 |
| semantic 형용사 | /sɪˈmæntɪk/ | 시멘틱 |
| verbose 형용사 | /vəˈbəʊs/ | 자세한 정보 |
| walkthrough 명사 | /ˈwɔːk.θɹuː/ | 공략 |
이 영상의 문법
화자가 가장 많이 쓰는 문형을 영상 속 실제 표현과 함께 정리했습니다.
| 문형 | 영상 속 표현 |
|---|---|
| 현재완료 have/has + 과거분사 — 과거의 일이 지금도 관련이 있을 때 | has definitely become · I've been asked · has become |
| 수동태 be + 과거분사 — 누가 하는지보다 무슨 일이 일어나는지에 초점 | I've been asked · being alphabetized · is finished |
| 관계절 who / which + 절 — 사람이나 사물에 대한 추가 정보 | Zod, which is · point, which makes · dev, which is |
주의할 발음
화자는 you're, doesn't, don't 같은 축약형과 약화된 형태를 25번 사용합니다. 들리는 대로 짧게 발음하세요.
- “th” 소리: walkthrough /ˈwɔːk.θɹuː/, altogether /ɔl.tuˈɡɛð.ɚ/, underneath /ˌʌndɚˈniθ/
- “sh”와 “zh” 소리: validation /ˌvæl.əˈdeɪ.ʃən/, deletion /dɪˈliːʃən/, friction /ˈfɹɪkʃən/, configuration /kənˌfɪɡ.əˈɹeɪ̯.ʃən/
- 긴 단어 — 강세 위치에 주의: ecosystem /ˈikoʊˌsɪstəm/, validation /ˌvæl.əˈdeɪ.ʃən/, interactive /ˌɪn.tɚˈæk.tɪv/, alphabetical /ˌæl.fəˈbɛt.ɪ.kəl/, asynchronous /eɪˈsɪŋ.kɹə.nəs/
이 영상으로 연습하는 방법
- 먼저 말하지 않고 영상을 끝까지 듣고 모르는 단어를 적어 둡니다.
- 0.75배속으로 한 문장씩 섀도잉을 시작하고, 익숙해지면 보통 속도로 돌아갑니다.
- 자신의 목소리를 녹음해 원본과 비교하고, ecosystem, beginner, rename 같은 단어에 특히 주의합니다.
쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법
쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.