Effective PyCharm Transcripts
Chapter: Why PyCharm and IDEs?
Lecture: IDEs are crazy fast
0:00 I'd like to dispel a myth around IDE's.
0:02 That they're slow.
0:04 You might think well these are heavyweight applications.
0:07 They take a lot of RAM.
0:08 They take a lot of disk space,
0:10 they're going to start slow. They're going to be the sluggish things,
0:13 man. Just give me some Emacs,
0:14 that thing starts up like that and it just flies. Well.
0:19 Yes. In some way starting a program that is large,
0:22 like an IDE from scratch that does take a little bit of time
0:24 Something like Emacs that just runs in a terminal probably starts faster.
0:29 But when you say something is slow and something is fast,
0:32 you've got to identify what you're making fast and what you're making slow.
0:36 I think with these very lightweight tools that start super fast.
0:39 Yeah, the program starts fast but then you work slowly and with less understanding and
0:44 less support throughout the rest of your day.
0:48 On the other hand, Richer tools like PyCharm and to be honest
0:51 VS code in terms of its speed of starting start slower but then for the
0:55 rest of the time for the other seven hours,
0:58 59 minutes and 55 seconds after that brief five second startup,
1:02 you have something that is actually faster because it helps you work much much faster.
1:07 So what do you want to optimize?
1:09 I would think you want to optimize your speed,
1:11 not your applications at speed. Another one is that because these programs are heavyweight,
1:17 they might use a lot of energy and if you're on battery or if you're on
1:21 a very wimpy system, Maybe you don't want that if you're at a coffee shop
1:24 or an airplane, you're down to your last 10% of battery.
1:28 Maybe you don't want to run a program that's going to do a lot of indexing
1:31 and analysis in the background. So let's jump over to my Mac real quick and address
1:36 both of these. Here we are in PyCharm and I've already loaded it up
1:39 but I don't have any projects open
1:40 Files. Projects. Remember here's a project that we're going to use during the
1:45 editor chapter. We're going to do some code with me,
1:48 which is super fun. When do that with brian Hawkins.
1:50 I want to open up this project.
1:53 How long will it take? Because the audio editing you probably won't hear the click
1:57 and so I'm gonna do a countdown.
1:58 I'll go 321 go. And then I want to say,
2:01 go, I'll try to click at that very exact moment.
2:04 Alright, here we go. 321 go.
2:07 How long did that take? 300 milliseconds.
2:10 350. I don't know. I didn't time it exactly,
2:12 but wow. Was that fast.
2:13 Let's do it again. 321 Go.
2:18 Yeah. That doesn't feel like a program that slow or painful to work with.
2:21 To me, that looks incredibly fast actually.
2:23 Right. So, yeah, you gotta wait the five seconds for the app to
2:26 start up maybe. But then for the rest of your day,
2:29 it is a blazing vast experience.
2:30 Just like all the others. All right.
2:32 So, I really don't think that this idea that this larger program is slow.
2:36 It has any merit, especially once you think about the trade off of getting all
2:41 of the support of the tool gives you. Second is if you are under your last
2:45 10% and all that indexing analysis is actually putting a hurt on your computer,
2:50 what can you do? Well,
2:51 there's this thing called power save mode and I could go to file and click it
2:55 But it's cool to just use the little help search.
2:56 Here's all type power and it'll show me all the things that have to do with
2:59 power here in the menu and check that out in power save mode.
3:03 If I go and I click that,
3:04 it's going to turn off some of the analysis and some of the indexing and use
3:09 less power less battery and so on.
3:12 So if you're in a super limited environment or you're down trying to squeeze that last
3:15 bit of battery out. You can also use power save mode and this application won't
3:19 take nearly as much. There you have it.
3:22 That's my case. The IDE's.
3:23 are actually faster because they make the developer faster without too much overhead