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