 Summers, I want to clear some things up, and that is I am not anti-Python. I have nothing against Python. Python is a great language, plenty of my favorite programs are written in Python, I have nothing against it. I say this because a couple weeks ago I did a video, it was actually on NNN, the file browser, where I committed terrible microaggressions against Python. I said, you know, the entire Python internet defense force came out against me, and oh how injured they were, because I got them right where it hurts, I said terribly that Python is a slow language, and that of course, you know, opens the floodgates, so all kinds of, I don't know, there are many people out there who use Python who are very attached to it, and although I wasn't trying to tell them not to use it, a lot of people get insulted when you call their language slow. So this video, well first off, on that point, no one can really, I guess dispute the fact that Python is one of the slowest languages out there that people actually write stuff in. I don't think you can, yeah, you can't really see my computer screen, but I'll send you the links, there is a nice little site where they do some benchmarking of many different programs, and of course compare the speeds at which they do things. So if you, for example, look at how quickly it takes, they have a Mandelbrot test, which I think is generating a Mandelbrot series or whatever you call it, to do that in C, if you write that in C and compile it with GCC, that takes 1.64 seconds, not very long at all, less than two seconds, that's a pretty fast execution. If you run the same thing in Python, if you write in Python and run it, that takes how many seconds? It takes 263 seconds, .04, much, much, so C it takes less than two seconds, Python it takes more than four minutes. I did pick the one that's right at the top, you can't really see it, but there are many dozens of other tests where Python is not just, it's not like 20% slower than C, and it's also not just C that it's slower than, you can compare it to PHP, you can compare it even to ODE's JavaScript, and Python is slower than all of them, not just by 20% or something, but often by tens of times or hundreds of times slower, maybe even thousands of times, you can check yourself. So Python is a slow language, but there is one good reason to use Python, and I'll talk about that just in one second, but before we even talk about that, let's have a kind of computer science 101 discussion here. Now, when you think about programming or scripting or whatever, you have to think of it as a kind of translation algorithm or something like that, a translation process, and what I mean by that is you have ideas in your brain of what you want the computer to do, and you have to put them in words that the computer can understand. Now, computers do not actually understand languages per se, they have to be converted to, well, at least not Python or even C, they have some kind of machine code that you have to convert whatever you're writing in into. Computer languages are crutches that we rely on to get into the actual assembly code or whatever else, which is more lower level. Now, C is a low level language, meaning it isn't necessarily a language, if you look at C code or if you have it explained to you, there are a lot of things that strike you as a little arbitrary, and that's because a lot of things that exist in C exist because they exist, they are priors of machine code or assembly or whatever, and C is a language written at a low level so it can be really run fast and run sonic fast on computers, whereas Python, on the other hand, when you think of programming as being kind of a translation algorithm, Python is closer to the human brain on that side of the algorithm or process, I guess, assembly line, if you will, and that is, Python is a language that is, I guess, I mean, I said it before in the other video, Python is basically pseudocode. It's written, it's constructed in a way for it to be easy for people to pick up and read it transparently. That's why they teach it in computer science 101 courses. Python is an intuitive language. It makes sense to people. So that is, but the downside of that, of course, is when you have Python code and you interpret it, that is a much more intensive process because the priors of Python are not necessarily the priors and constructs of some machine code, whereas that's the disparity is much less when you're writing something in C and compiling it. So that's one of the reasons that Python is, now, I said before, there is a one good reason to use Python and it's sort of what I just mentioned, and that is Python is easy. That is the one reason that people use Python. Now, don't get me wrong. If you use Python and you don't like how that sounds, you will say something else. You'll tell me something like, oh, well, I use Python because it just makes the development process easier and more transparent and blah, blah, blah. Okay, but what that means is Python is easier. It's easier for people to pick up. It's easier for people to debug code because it's very transparent. In the same way, people will say, oh, there are all these great packages written for Python. Well, first off, a lot of the libraries and stuff that are available for Python are available for any other language, but even if that's true, mind you, why do people write things for Python? They do it because it's a relatively simple language to get into. Same thing, why is Python, every passing year, Python seems to become a more and more popular language. Why is that? It's because Python is easy. All the reasons that people use Python boil down to that. Python is an easy language. There's nothing to be, it doesn't mean you're less good because you're writing it. Now, I will say, I'm not saying that everyone should write in C or everyone should write in some low-level language, absolutely not. But the way I think of it, well, I don't write in Python myself, but I'll explain why in a second. But you have to really think of, when you're dealing with computer, there are two different tasks you're doing. One is writing really hardcore intensive programs. And when you do that, if you had to force me to do that, I would prefer to write something in C. It might be more difficult, but when you're writing something that's really big and people are gonna be running stuff on top of it, it's nice to have a quick, very snappy and responsive program. That's why it's very sensible to write a big program in C and less sensible, again, some of my favorite programs are written in Python, Ranger, Q-Browser, but these programs are noticeably less responsive, partially because of that. So there are sometimes where you're writing hardcore programs where you really want to use a lower-level language, but when you're doing things that's just like scripting or just writing either a shell script or just something random that isn't gonna be that intensive, that's an appropriate time to use a language that's closer to Python. Now, I myself do not use Python. And the reason I don't is when I'm doing that kind of high-level stuff, when I'm doing basic scripting, I prefer to use shell scripting. And I will say a lot of people who get into Linux or Unix or whatever, a lot of people because they'll take computer science 101 and nowadays everyone learns Python in that class, because they do that, they glom on the Python and wanna write all their scripts in Python for their system management. And I think that's a bad idea. And mind you, I started doing that too when I first started using Linux. I used Python for everything or tried to use Python for everything because I understood it, it's an intuitive language and it's what a lot of other people use for stuff. But when it comes to the system, actually getting things done elegantly and having them all meld well together, I find that it's much more useful when you're just doing scripting to just write in a shell script. POSIX compliant shell or just bash, if you need some good bashisms. Technically, those are different, some people get confused. That's for another video, but bash is not the same thing as shell. Well, anyway, we'll talk about that in another video. But that's what I do because when you're reading stuff from standard input or standard output or you wanna chain commands together, pipe everything together, it is just so much easier to do things in shell than it is to do things in Python. You can, of course, do that kind of stuff in Python. It's just nowhere near as elegant. So anyway, that is my, I don't know, my statement on it. Oh, and I will say one, well, let me throw on one more thing because I meant to talk about this. There are other ways, if you really just love the syntax of Python, there are things like, for example, Scython, which you may have heard of. Some people even brought it up in the video comments, but what Scython is, in case you don't know, is it's, I guess it's sort of its own language, but it's really nearly equivalent to Python, but it's a compiled language where you write your code and then it in effect converts it or compiles it into C and then runs from there. So I've never used Scython myself, but I will say that is an option out there if you're the kind of person who is just really attached to Python code or maybe you just really want something intuitive, but you do want the speed of C or something else like that. So anyway, that's it. Now again, there's no shame in using a language because it's relatively simple. I'm not dabbing on people saying that they use Python because it's easy. That's a totally legitimate reason, but I don't necessarily think it's a very good habit to get in, get in a mindset where you're constantly writing all these big programs in Python because I mean, what's it gonna lead to? Are we gonna have entire operating systems written in Python, a language that does a lot of the more complex operations, like hundreds of times slower? That's not necessarily a good future, but nowadays you never know. So anyway, that's about it. Again, I didn't mean to offend any Python users, but that is my justification of what I said and I don't take any of it back. Obviously, so that's it.