The most used and well documented programming language for web development is PHP, but it has some problems as a language (every language does)….

Point 4, 5, 7, 9, 10 and 17 we agree so I won’t say anything more about them

1.
The reason I’ve said to use var_dump is because sometimes installing a debugger can be hard. In a usual code var_dump is pretty enough, and sometimes is more comfortable because you can type 20 variables in the same line.

2.
That function is a little bit old, but, yes, that parameter make things easier. According to the file, of course it’s better having a class, but it’s just an example and the reason why I put those functions in a file is just for making the final code cleaner.

3.
The problem is as developers we come from many languages, and if we are used to develop with a style it’s difficult to change it. Standards are ok, but getting used to them can be a long process. With my advice I just meant we should respect a pattern, not forgetting about standards.

6.
I suspect we are not talking about the same thing here. The point is to notice that we usually use “two false” when it’s easier just use a true. I’m not talking about the meaning of enable or disable.

8.
Actually I haven’t shown the actual point of having getters and setters, it was just the syntax. But having setters and getters can be useful for having a password where users can set it but not seeing its content, having a username where you can get the value but not setting it…and many others. But it’s perfectly correct, of course you can generate with a function dynamic setters and getters, but that’s a little bit harder and I just wanted to show the “classic” way.

11.
Character encoding is the correct term, but actually it seems clear when I’m talking about é characters in the next paragraph.

12.
I don’t know if you’re trying to say I don’t know OO, or just putting a link. Here I meant that when we build classes we have always to try make them as independent as possible, but when we have someone’s classes, then everything can happen and checking exceptions or errors coming from that class is a must.

About the two 12′s sorry, it was my mistake, and thank you for letting me know it.

13.
I thought when I was writing this that “interface” could be misunderstood. I meant interfaces as in an API or a control panel, that means methods which allow us to access to the class and give us some kind of responses. Not the OO term of interface, which is a very different thing.

15.
Good advice! But I was just trying to notice that we have to take care of the variables we are using.

16.
Family is just a term to mean we have to use the Object Oriented feature that PHP has. Of course I could put a lot more examples but the one I put is related and based on that feature. Perhaps I had to put another showing how to use the abstract concept in PHP.

18.
I think we should know how to do a thing if we are using a class which does. That means if we are using a framework as CodeIgniter we should be able to develop all the framework (or at least the part we are using) by ourselves and using the framework is just for saving time. Of course sometimes it’s better think about what we need and if we really have to use a framework for that.

As I’ve said before, thanks for the comment!