Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated:
1
00:00:01,930 --> 00:00:09,460
What problem or problems do you see with everybody creating their own engines in JavaScript, just like
2
00:00:09,460 --> 00:00:09,940
we did?
3
00:00:09,940 --> 00:00:10,480
Right?
4
00:00:10,780 --> 00:00:15,100
Can we just create our own engine and all of a sudden, boom, there it is.
5
00:00:15,100 --> 00:00:16,510
We have our JavaScript engine.
6
00:00:17,260 --> 00:00:19,390
Well, yes, you can definitely do that.
7
00:00:19,780 --> 00:00:27,520
But remember our list over here how it was called script engines and not JavaScript engines.
8
00:00:28,670 --> 00:00:34,800
That's because if everybody can just create a JavaScript engine, it'll just be total chaos, which
9
00:00:34,800 --> 00:00:36,930
is why a script was created.
10
00:00:37,500 --> 00:00:43,620
It tells people, Hey, here's the standard and how you should do things in JavaScript and how it should
11
00:00:43,620 --> 00:00:44,220
work.
12
00:00:44,760 --> 00:00:52,110
And the script is the governing body of JavaScript that essentially decides how the language should
13
00:00:52,110 --> 00:00:53,070
be standardized.
14
00:00:53,720 --> 00:01:02,810
So it tells engine creators this is how JavaScript should work, but internally how you build the engine
15
00:01:02,810 --> 00:01:06,470
is up to you as long as it conforms to the standards.
16
00:01:08,180 --> 00:01:15,140
And if we go back to our example over here, this engine inside of this box, as long as it conforms
17
00:01:15,140 --> 00:01:21,020
to my script standards, I can do whatever I want as an engine creator.
18
00:01:21,780 --> 00:01:28,500
So companies and organizations are battling to have the fastest engine so people use their tool.
19
00:01:28,680 --> 00:01:34,680
For example, Google is really interested in having the fastest engine so that more people use their
20
00:01:34,680 --> 00:01:40,350
Chrome browsers, so that they use their search engine so that they can sell more ads and make more
21
00:01:40,350 --> 00:01:40,920
revenue.
22
00:01:41,650 --> 00:01:49,300
But keep this in mind that this can be implemented any way we want and it constantly changes to find
23
00:01:49,300 --> 00:01:56,260
the fastest way possible to have JavaScript work in our browsers or even outside of our browsers.
24
00:01:57,120 --> 00:02:01,980
And we're going to be talking about the V8 engine here because it is the most popular.
25
00:02:02,100 --> 00:02:05,040
And you might see some different variations of this.
26
00:02:05,040 --> 00:02:10,560
But what we're going to talk about here applies to most JavaScript engines.
27
00:02:11,130 --> 00:02:17,490
And although things may change over time, as long as you understand the principles and why it's built
28
00:02:17,490 --> 00:02:21,900
the way it is, we're going to be able to understand how to write optimized code.
29
00:02:22,410 --> 00:02:26,400
But before we get into that, let's talk about what these things are.
30
00:02:26,430 --> 00:02:29,010
We have the interpreter and the compiler.
31
00:02:29,780 --> 00:02:31,280
I'll see you in the next video.
32
00:02:31,580 --> 00:02:32,150
Bye bye.
3298
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.