Your videos are really awesome and easy to understand. You explain different theories of programming with good examples. I hope in the future, you will make more videos about programming and on Java. Keep up the good work!
+Zhendong Liu Hello and thank you very much for your comment! Unfortunately I tend to keep away from syntax related videos since (unlike CS1020), my main focus is on concepts and theories, and making them easier to understand! Hopefully most of the things here will still remain applicable though, since if you can see the big picture (which is what I'm aiming for), then learning the actual algorithms will become easier.
Why are you so much better than my professor? Nicely done. I learned more in your short chapter than 50 pages of my book and 4 hours of professor lecture
Hello and thank you very much for your comment! I'm a lot less formal and precise than in a classroom setting, that's probably why. Take this as a primer to the subject matter, but absolutely do revisit your class content, which I'm sure goes into much further depth and is more actionable!
Can I suggest a video topic? The keyword static. I have and watched videos about it and still don't understand what exactly it is and when is it necessary to use.
+Swiizzey Oooh, that is definitely a good thing to talk about! But for now, let me answer your question in text, because I don't know when is the next time I'll get to shoot a video. A static function is associated with the *class*, while non-static functions are associated with *objects* (ie. Individual instances of a class). So for the ball example shown in the video, "kick" is associated with the individual balls, ie you can kick _a_ ball, but you can't kick the _definition_ of ball. If we like, we can add some things to the existing class, perhaps in this form: class Ball { private static int count = 0; public Ball( ... ) { ... count++ } public static int getCount() { return count; } } Meaning, every time I create a new ball, the count increases by one. Clearly, "count" is an information that cannot be associated with instances of the Ball class (I couldn't look at _one_ ball and somehow figure out how many balls there are in the world). However, because this information is held by the ball *class*, I can simply query this at any time, by saying Ball.getCount(). The count is information associated with the *class*. Is this clear enough? I think I got a bit too rambly there. Let me know if you need any further clarification.
Hey, could you consider make a video about object recognition using classifiers (can be opencv) and/or how train your classifier :) Anyway, Will be not bad idea to do a set of videos explaining methods of pattern recognitions :)
+Hypnosiss Hello and thank you for your comment! I am currently taking a course in school on computer vision and pattern recognition, and to be honest, waaay too much of it is going over my head for me to be confident in doing a video on it! When it comes to recognition using classifiers, well, machine learning is one of the things furthest outside my specialization too, so I'm worried I wouldn't be able to provide much insight. However having said that, I did make a video on machine learning (very much in general), and I did actually set up an experiment on very simple shape recognition in that video. I don't go into detail on _anything_ really, so it's probably not what you're looking for. But if you'd like to check it out, here it is: ua-cam.com/video/REaLt09fD80/v-deo.html
Hey! I am also taking a course at my university :) Field is quite interesting in particulary that is continously deploying around us (number plate recognition, traffic analyzing, products recognition et cetera). If you have some more knowledge about it, share with others it will be very usefull, specially if it is explained explicitly :) Thanks for a link!
+Hypnosiss I'll see what I can do! Like I said a lot of it is going over my head so I don't know how much I'm confident to speak about, but I can probably talk about the more basic stuff.
That balltest array is just an array of pointers, isn't it? Otherwise you wouldn't have been able to instantiate the subclasses because there might not have been enough memory allocated, right?
+Shadow4707 Hello and thank you for your comment! That is indeed correct. I'm no expert at this, but from what I understand, in Java we can assume everything is a reference of some kind. So yes, there will be some logisitical difficulties if this was not the case.
Hello and thank you for your comment! Firstly - Be careful of your terminology! When we're talking about inheritance, we're talking about building *class* definitions that inherit off another class! Therefore when we're going on about parent/child relationships, they must be in relation to classes, *not objects*! Anyway to answer your question - A parent class can certainly be a child class, and vice versa - But not of each other! Take a look at this example: Animal → Mammal → Cat. Mammal is the child class of Animal, and the parent class of Cat. However, you cannot have a class that is both the parent and child of another class. This creates a cyclic inheritance that can never be made sense of!
Hello again! Please clarify on your question "Isn't a child object IS A also a parent object? But isn't a parent object IS NOT A child object?" - As explained above, a child (or sub-) class, can be the parent (or super-) class of another object. And yes, in Java, every class extends the Object class, and as such every class is a subclass.
![[UA] NAVI vs MOUZ | BO5 | IEM Rio 2024](http://i.ytimg.com/vi/CMBYk0cbGoA/mqdefault.jpg)
Thank you so much! was really waiting for this!
Your videos are really awesome and easy to understand. You explain different theories of programming with good examples. I hope in the future, you will make more videos about programming and on Java. Keep up the good work!
+Zhendong Liu Hello and thank you very much for your comment! Unfortunately I tend to keep away from syntax related videos since (unlike CS1020), my main focus is on concepts and theories, and making them easier to understand! Hopefully most of the things here will still remain applicable though, since if you can see the big picture (which is what I'm aiming for), then learning the actual algorithms will become easier.
Why are you so much better than my professor? Nicely done. I learned more in your short chapter than 50 pages of my book and 4 hours of professor lecture
Hello and thank you very much for your comment! I'm a lot less formal and precise than in a classroom setting, that's probably why. Take this as a primer to the subject matter, but absolutely do revisit your class content, which I'm sure goes into much further depth and is more actionable!
So much useful information packed into such a short video. Love it!
Hello and thank you very much for your comment! Very happy to be of help :)
My favorite & goto channel whenever I need something explained again
Hello and thank you very much for your comment and support! Glad to be of help =)
This cleared up a lot of things for me! You saved me a lot of frustration. Thank you!! :D
You're welcome! Very happy to be of help =)
so much better than the slides in my java class, thanks
You're welcome! Glad to be of help =)
Very good explanation. Very clear. Cheers!!!
Hello and thank you very much for your comment! Glad you liked the video =)
5:09 I agree
Heh! Couldn't resist slipping in that line =P
hahaha
Can I suggest a video topic? The keyword static. I have and watched videos about it and still don't understand what exactly it is and when is it necessary to use.
+Swiizzey Oooh, that is definitely a good thing to talk about! But for now, let me answer your question in text, because I don't know when is the next time I'll get to shoot a video.
A static function is associated with the *class*, while non-static functions are associated with *objects* (ie. Individual instances of a class). So for the ball example shown in the video, "kick" is associated with the individual balls, ie you can kick _a_ ball, but you can't kick the _definition_ of ball.
If we like, we can add some things to the existing class, perhaps in this form:
class Ball {
private static int count = 0;
public Ball( ... ) {
...
count++
}
public static int getCount() {
return count;
}
}
Meaning, every time I create a new ball, the count increases by one. Clearly, "count" is an information that cannot be associated with instances of the Ball class (I couldn't look at _one_ ball and somehow figure out how many balls there are in the world). However, because this information is held by the ball *class*, I can simply query this at any time, by saying Ball.getCount(). The count is information associated with the *class*.
Is this clear enough? I think I got a bit too rambly there. Let me know if you need any further clarification.
Yeah now I understand it much better. Thanks m8
+Swiizzey Cheers! Glad to be of help =)
0612 TV w/ NERDfirst nice you rock at explaining.
Best explanation ever saw :)
Hello and thank you very much for your comment! Very happy to be of help =)
Hey, could you consider make a video about object recognition using classifiers (can be opencv) and/or how train your classifier :) Anyway, Will be not bad idea to do a set of videos explaining methods of pattern recognitions :)
+Hypnosiss Hello and thank you for your comment! I am currently taking a course in school on computer vision and pattern recognition, and to be honest, waaay too much of it is going over my head for me to be confident in doing a video on it! When it comes to recognition using classifiers, well, machine learning is one of the things furthest outside my specialization too, so I'm worried I wouldn't be able to provide much insight.
However having said that, I did make a video on machine learning (very much in general), and I did actually set up an experiment on very simple shape recognition in that video. I don't go into detail on _anything_ really, so it's probably not what you're looking for. But if you'd like to check it out, here it is: ua-cam.com/video/REaLt09fD80/v-deo.html
Hey! I am also taking a course at my university :) Field is quite interesting in particulary that is continously deploying around us (number plate recognition, traffic analyzing, products recognition et cetera). If you have some more knowledge about it, share with others it will be very usefull, specially if it is explained explicitly :)
Thanks for a link!
+Hypnosiss I'll see what I can do! Like I said a lot of it is going over my head so I don't know how much I'm confident to speak about, but I can probably talk about the more basic stuff.
That balltest array is just an array of pointers, isn't it? Otherwise you wouldn't have been able to instantiate the subclasses because there might not have been enough memory allocated, right?
+Shadow4707 Hello and thank you for your comment! That is indeed correct. I'm no expert at this, but from what I understand, in Java we can assume everything is a reference of some kind. So yes, there will be some logisitical difficulties if this was not the case.
+lcc0612 Everything is reference except for primitive types (default types that start with lowercase letter i.e..: int, double...)
+TheAl_T Thank you for your comment! I forgot about the primitive types, but yes, that makes a lot of sense =)
OMGGGG WHY DID'NT SEEE THIS BEFORE , THANKS MAN MAKE IT ON GUI JAVA PLS
You're welcome! I'm not an expert on Java GUI to be honest, but I'll see what I can do!
Nice video bro!
Hello and thank you for your comment! Glad you liked the video =)
Good content
Hello and thank you for your comment! Glad you liked the video =)
great videos
+Alexander Bollbach Thank you very much! Glad you like my work =)
1. is a child object also a parent object? 2. is a parent object also a child object?
Hello and thank you for your comment! Firstly - Be careful of your terminology! When we're talking about inheritance, we're talking about building *class* definitions that inherit off another class! Therefore when we're going on about parent/child relationships, they must be in relation to classes, *not objects*!
Anyway to answer your question - A parent class can certainly be a child class, and vice versa - But not of each other! Take a look at this example: Animal → Mammal → Cat. Mammal is the child class of Animal, and the parent class of Cat.
However, you cannot have a class that is both the parent and child of another class. This creates a cyclic inheritance that can never be made sense of!
Isn't a child object IS A also a parent object? But isn't a parent object IS NOT A child object?
is every Java class a subclass???
Hello again! Please clarify on your question "Isn't a child object IS A also a parent object? But isn't a parent object IS NOT A child object?" - As explained above, a child (or sub-) class, can be the parent (or super-) class of another object.
And yes, in Java, every class extends the Object class, and as such every class is a subclass.