Big difference between procedural and objected oriented php is that you didn't say "because... why not". I liked that in earlier videos. Thanks for the uploads.
I just started watching yours tutorials. I'm really impressed how you try to share your knowledge. Can you share what text editor you are using during the tutorial? Thanks in advance.
could be bad acoustics in your listening environment, you'll lose some consonant definition because ...standing waves... that can explain why only a few hear it like that, where on studio monitors he clearly says object oriented lol
Hey, Keep up the good work. One suggestion, sometimes you speak very fast and also doesn't sound clear, no clear pronunciation (only few places). Just a feedback from non-native English speaker. Overall, thanks again, its helping me a lot.
If you use the function var_dump() in php, it will give you additional information about the contents it shows. For example it will tell you that the property in this case is of type string and has the length of 17 characters. If it was the number 143 it would say int(3).
Please provide real life scenarios when providing explanations. It's like explaining grammar to a child - let them play around with real life examples and then explain properties, methods etc (similar to grammar). The most important thing is application !!! Why create classes, what's the rational behind creating classes !!! Auction houses use PHP classes for bids etc. so use real life examples.
Another way to explain methods vs functions is, a method is exactly just a function but because it is inside of a class now it is called method. function outside a class = function function inside a class = method method outside a class = function method inside a class = method
That is correct when you look from the structural point, or the code itself. From the point of oop/functional programming, then functions should not modify any state, only take input and return the output. While method is encouraged to actually change its object state, rather then receiving and giving back the output. That is why he says they are not the same, not because the code is written differently but more because of the context they apply to
There is no inherent logic behind the naming of PHP files in PHP. The name 'class.inc.php' indicates that it's a file you include and don't call on its own. However, you can actually give this file any name you want.
You can only include a specific file once per page load if you use include_once. This is a way to ensure that you do not load the same file multiple times, which can slow down loading time, or even cause errors.
MVC (Model-View-Controller) is an architectural pattern that separates an application into three main components: Model, View, and Controller. The Model manages data and business logic, the View displays information to the user, and the Controller handles user input, processes requests, and coordinates between Model and View. In a web application using MVC, a user's request is routed to the appropriate Controller, which processes the request and interacts with the Model to fetch or manipulate data. The Controller then prepares this data and selects an appropriate View. The View renders the output using the data from the Controller, which is then sent back to the user's browser. This pattern promotes separation of concerns, allowing for modular development and easier maintenance. Think of MVC like a restaurant: - The Model is the kitchen - it handles all the ingredients and cooking. - The View is the dining area - it's what customers see and interact with. - The Controller is the waiter - it takes orders from customers, tells the kitchen what to make, and brings the food to the tables. When you visit a website, it's like entering the restaurant. Your request goes to the Controller (waiter). The Controller might ask the Model (kitchen) for information, then chooses and prepares a View (like arranging food on a plate) to show you. This setup keeps everything organized - the kitchen doesn't serve customers, the dining area doesn't cook food, and the waiter coordinates it all. Structure wise frameworks usually have dedicated folders for each tier. In Laravel it's app/Http/Controllers/, app/Models/ and resources/views/. In Symfony /src/Controller, /src/Entity and /templates. In my own framework I'm making it's Controller/, Entity/, views/.
@@editotech7531 If your page is just comprised of php then the closing tag is not needed. If it contains HTML or JavaScript, for example, then you need to use the closing php tag after each block of php.
stop.. saying.. actually.. please. it's a special word used to accentuate something that may from some angle be unbelievable. otherwise thank you and great tutorial!
your use of newClass is not very descriptive and makes it harder for newbies. Call it bluePrint or baseClass. Then create a new instance of this class.
I can't tell with your "bold" comment, if you are making fun of my English speaking, or if you seriously think I am saying "optic" instead of "object"...
