All language subtitles for 077 React Optimization Warning!!!!.en_US

af Afrikaans
sq Albanian
am Amharic
ar Arabic
hy Armenian
az Azerbaijani
eu Basque
be Belarusian
bn Bengali
bs Bosnian
bg Bulgarian
ca Catalan
ceb Cebuano
ny Chichewa
zh-CN Chinese (Simplified)
zh-TW Chinese (Traditional)
co Corsican
hr Croatian
cs Czech
da Danish
nl Dutch
en English
eo Esperanto
et Estonian
tl Filipino
fi Finnish
fr French
fy Frisian
gl Galician
ka Georgian
de German
el Greek
gu Gujarati
ht Haitian Creole
ha Hausa
haw Hawaiian
iw Hebrew
hi Hindi
hmn Hmong
hu Hungarian
is Icelandic
ig Igbo
id Indonesian
ga Irish
it Italian
ja Japanese
jw Javanese
kn Kannada
kk Kazakh
km Khmer
ko Korean
ku Kurdish (Kurmanji)
ky Kyrgyz
lo Lao
la Latin
lv Latvian
lt Lithuanian
lb Luxembourgish
mk Macedonian
mg Malagasy
ms Malay
ml Malayalam
mt Maltese
mi Maori
mr Marathi
mn Mongolian
my Myanmar (Burmese)
ne Nepali
no Norwegian
ps Pashto
fa Persian
pl Polish
pt Portuguese
pa Punjabi
ro Romanian Download
ru Russian
sm Samoan
gd Scots Gaelic
sr Serbian
st Sesotho
sn Shona
sd Sindhi
si Sinhala
sk Slovak
sl Slovenian
so Somali
es Spanish
su Sundanese
sw Swahili
sv Swedish
tg Tajik
ta Tamil
te Telugu
th Thai
tr Turkish
uk Ukrainian
ur Urdu
uz Uzbek
vi Vietnamese
cy Welsh
xh Xhosa
yi Yiddish
yo Yoruba
zu Zulu
or Odia (Oriya)
rw Kinyarwanda
tk Turkmen
tt Tatar
ug Uyghur
Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated: 1 00:00:00,150 --> 00:00:00,900 Excellent work. 2 00:00:00,930 --> 00:00:04,420 And up next, we have performance optimization. 3 00:00:04,800 --> 00:00:09,030 More specifically, we're going to cover react and more function. 4 00:00:09,510 --> 00:00:14,490 You should call back hook and then use Memmo Hook as well. 5 00:00:15,060 --> 00:00:23,190 Now, before we go any further, let me just be very, very clear where I purposely added this topic 6 00:00:23,190 --> 00:00:24,770 to be our last one. 7 00:00:25,260 --> 00:00:25,740 Why? 8 00:00:26,130 --> 00:00:29,550 Because react is fast by default. 9 00:00:29,980 --> 00:00:31,350 Again, let me repeat. 10 00:00:31,950 --> 00:00:34,310 React is fast by default. 11 00:00:34,860 --> 00:00:43,800 And what I mean by that is just because you have these tools to optimize the performance of your app 12 00:00:44,070 --> 00:00:49,530 doesn't mean that you need to run over to your to do list app and start optimizing. 13 00:00:49,720 --> 00:00:51,060 That's not how it works. 14 00:00:51,330 --> 00:00:54,720 Now, I did include it and by the way, I was debating back and forth. 15 00:00:55,020 --> 00:00:56,340 I almost skipped it. 16 00:00:56,610 --> 00:01:03,810 But I did include it in editorial because I wanted you to be aware of these functions and hooks and 17 00:01:03,810 --> 00:01:04,770 how they work. 18 00:01:05,520 --> 00:01:09,900 But it doesn't mean that you need to use them in your apps. 19 00:01:09,920 --> 00:01:13,950 Yes, there are some specific use cases where they are useful. 20 00:01:14,400 --> 00:01:22,110 But trust me when I say this, just because Twitter Gurel says that you need to apply these optimizations, 21 00:01:22,410 --> 00:01:23,460 you have to do it. 22 00:01:23,700 --> 00:01:26,190 No react as fast by default. 23 00:01:26,400 --> 00:01:30,390 And when it comes to optimisations, they do their own costs. 24 00:01:30,960 --> 00:01:36,900 So it's not like it's a free ride where we just have these magic functions and everything works like 25 00:01:36,900 --> 00:01:37,290 features. 26 00:01:37,710 --> 00:01:39,150 They do use the memory. 27 00:01:39,150 --> 00:01:41,160 They do use the competition power. 28 00:01:41,460 --> 00:01:45,180 So be mindful when you actually use them. 29 00:01:45,540 --> 00:01:50,820 During the videos, I will mention term memorialising and that is not my term. 30 00:01:50,820 --> 00:01:51,790 That is not react. 31 00:01:52,320 --> 00:01:56,940 That is a computer science term, which just means that we're caching results. 32 00:01:57,180 --> 00:02:03,690 And I'll simplify it even more during videos where I'll say, remember, we're remembering the value. 33 00:02:04,080 --> 00:02:10,740 Just keep in mind what the official naming is, because, of course, remembering is something that 34 00:02:10,740 --> 00:02:16,230 I added because I thought that we should simplify this memorizing term. 35 00:02:16,650 --> 00:02:18,870 And then lastly, if you don't trust me. 36 00:02:19,790 --> 00:02:26,540 If you think that everything that I'm saying is gibberish and that you should use all of these functions, 37 00:02:26,900 --> 00:02:32,930 I would suggest going to your favorite search engine and just type use callback or use Memmo and then 38 00:02:33,110 --> 00:02:33,860 type count. 39 00:02:34,250 --> 00:02:44,350 And you should get the article by Kent Dods, where essentially he talks about when you should use Mammo 40 00:02:44,360 --> 00:02:45,790 and use Kovalchuk. 41 00:02:46,010 --> 00:02:47,860 And there's not much to add there. 42 00:02:47,870 --> 00:02:57,550 He just lays out step by step why you shouldn't go crazy, would use Memmo and use callback. 43 00:02:57,570 --> 00:03:01,100 OK, so that's what we're going to cover next. 44 00:03:01,430 --> 00:03:03,520 There's going to be, of course, an example. 45 00:03:03,830 --> 00:03:07,920 Now, I created that example with the specific purpose. 46 00:03:08,330 --> 00:03:14,630 Again, it's not normally where you would use these optimizations, but since I wanted you to have an 47 00:03:14,630 --> 00:03:20,930 idea of how they work and where you can use them, that's why I created. 48 00:03:21,020 --> 00:03:29,030 So we get a good practice on the Ariake memo as well as use callback and use memo. 4333

Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.