Summer Agenda in Detail
Hey guys, his Makinson on, and today I'm going to be giving you more information in detail about our summer agenda. I'm going to be going over what types of programming languages we're going to learn over the summer.
So first of all, of course, every once in a while, I kind of come out with the universal video that will probably be interesting to all of you. But for the programming, we're going to have two Morsi lessons. The two C lessons are going to be—we're going to make like a calculator-ish app and an app called High Low. Then we're going to move on to something called Perl. We're going to have two lessons on that, five or six Java lessons. Java works on everything, but we're going to be using Java for the Mac, and then 10 to 20 Mac or Mac Objective-C programming.
So we're going to be programming for the Mac using Objective-C, and then 10 to 20 iPhone Objective-C programming language lessons. So then we're going to have 25 web programming. So that's 25 about, so all these numbers are approximate. For web programming, I mean PHP, JavaScript, HTML, CSS. And since Ajax is a programming language, I can't say Ajax, but I'm going to be doing JavaScript—that's a jack C. So that's our agenda in more detail. I'll have it in the description of the video.
Also, I'll just go over what different types of programming languages are. There are two main types of programming languages: interpreted and compiled. Compiled is something that's interpreted by a compiler, which turns your code into C into code that can be handled by the processor—so that's compiled. So C is compiled; Objective-C is compiled. Everything pretty much that we're going to be learning uses the compile, and then it's rentable.
Then there is another type, interpreted, which is where a program runs your code, processes it while it's running it, and gives you a while turning it. Perl is an interpreted program; called Perl actually reads your file, your Perl script, and it processes it and handles it for you. If we have time, I might be doing a Mac Objective-C based interpreted language that we're going to make ourselves, but that's just a maybe if we have extra time at the end of the year summer.
So that's what those two are. Interpreted doesn't compile normally, since you're sending interpreted languages between each other. Like Perl, you can normally edit the script. Like, um, I believe that AppleScript is interpreted. So when you send someone like a Perl script, it's not only that PL file, and you can normally open that up with TextEdit and see the source code because it doesn't compile with the C program. It's compiled, so when you open it up with TextEdit, you can't really see the source code.
So all the programming languages we're going to be learning during the summer, except for Perl and PHP, HTML—all the web things are compiled. So only Perl and the web stuff is going to be interpreted. So those are the differences between interpreting and compile; those are our agenda.
Now I'm just going to tell you a few apps I made in Java. Java is what I used to make their original say; it's what I used to make the original edit on A1, which is kind of bad, I admit. Um, I made a lot of our apps with it, so Java is not half bad. Objective-C is what I use to make pretty much everything—Mac apps, iPhone apps, everything. And I'm working out a major Mac app that will hopefully come out eventually. It's an encryption algorithm that actually works, but so I'm going to come out with that eventually.
So Objective-C is the main one I use on my Mac. C I use on Linux. I don't use—I don't like C++. Bottom line is, I'm not going to teach you C++. There's no reason to use C++ if you can't do it in C. Then you should either do Objective-C or Java. If you're a Windows guy and you're using C++ on Windows, I'm not going to teach you C++ the Windows way because Microsoft took C++ and edited it, which is probably C++ .NET.
So if you're hoping on programming in C++ for Windows by learning C from here or C++ from here, you're out of luck. So we're not going to teach C++; it's either C or Objective-C. You have to decide if you want to use classes or not. There's no reason to use C++ if you can use Objective-C, so I do it. So I'm not going to be making any C++ languages.
Um, so those are the main languages. C is what I'm focusing on right now; there are two more, like I said earlier. And then, I know some of you hate C because it's unnecessarily hard, but it's good to get to know C because once you know some C and once you begin to understand it, it'll be easier—pretty intimate. It'll be easier for you to use Objective-C since it's mostly C; it'll be easier for you to use Java. Java and Objective-C are actually kind of like their library-wise, and don't be make easier for you to make iPhone apps.
Oh, that's so great, and that's what our agenda is. So thanks for watching. Makinson on—this is what our agenda is. And thanks for watching and goodbye!