शैडोइंग अभ्यास: 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
University StudentsBusiness English+1
C17
70 वाक्य
When open-sourcing your code goes wrong...
American Accent, en-USUniversity Students+2
C11
132 वाक्य
Video
University StudentsBusiness English+1
C11
218 वाक्य
Next.js 16.3 got good (if you care)
University StudentsBusiness English+1
C11
54 वाक्य
Traceroute: You're Probably Reading the Results Wrong
University StudentsBusiness English+1
C11
333 वाक्य
Master n8n Triggers in 20 Minutes – Automate Anything
University StudentsBusiness English+1
C12
195 वाक्य
JavaScript Visualized - Event Loop, Web APIs, (Micro)task Queue
University StudentsBusiness English+1
C11
189 वाक्य
Using AI to read research articles
University StudentsBusiness English+1
B21
64 वाक्य
JTBD Framework in UX w/ Examples | UXtweak
University StudentsBusiness English+1
C11
357 वाक्य
Everything You Need To Start Making Games (As A Beginner)
University StudentsBusiness English+1
B21
202 वाक्य
Is React Native Dead? Shopify Is Leaving
University StudentsBusiness English+1
C11
78 वाक्य
The easy way to keep your repos tidy.
University StudentsBusiness English+1
इस पाठ के बारे में
आप "Does Anyone Use JavaScript Anymore?" के साथ Shadowing तकनीक का उपयोग करके अपनी अंग्रेजी का अभ्यास कर रहे हैं।
शैडोइंग तकनीक क्या है?
शैडोइंग (Shadowing) एक विज्ञान-समर्थित भाषा सीखने की तकनीक है जो मूल रूप से पेशेवर दुभाषिया प्रशिक्षण के लिए विकसित की गई थी। विधि सरल लेकिन शक्तिशाली है: आप मूल अंग्रेज़ी ऑडियो सुनते हैं और तुरंत इसे ज़ोर से दोहराते हैं — जैसे वक्ता की छाया 1-2 सेकंड की देरी से। शोध से पता चलता है कि यह उच्चारण सटीकता, स्वर, लय, जुड़ी हुई ध्वनियाँ, सुनने की समझ और बोलने की प्रवाहशीलता में काफ़ी सुधार करता है।