Kingdom of Roi

First of all, I’m not against it. I do not understand why it does really matter what the namespace separator is.

What kind of difference will it create to use “/”, “”, “:::”, “;;;”, “{{}}” or whatever. Well of course that I do not like to use a namespace like “thisisnamespaceseperator”. It must be easy to use, and when you look at it, you should see that some things are separated. Why there are so much discussion about it that I do not understand.

Any of them is ok for me. I can use “:::” or “”, what’s the real matter about it, I do not honestly understand. I do not think there is huge difference with My:::Class:::Bar() and MyClassBar().

Perhaps that because I’m a rookie, I also do not understand why someone will think to use a new language just because of one decision. I respect everyone’s idea and if it does not look good to you, then you should be using something else. I hate Python’s code look. A programmig language without { and } does not look good to me. But I think that if I go over my prejudice, I will like it.

I love to write PHP. I even love how it’s written php, with two lines down and one lineup. I love the freedom of being able to write both OOP and functional application, I love the syntax of PHP, I enjoy helping people about PHP, I enjoy joining to seminars, conferences and community activities. That’s the real power of the PHP. Ruby has also a community but they are arrogant, they are doing with the ruby way and they feel special. Just like using Mac instead of a PC. You don’t like how the “” looks like, don’t worry you will get used to it.

I don’t want to say that this namespace seperator is the php way of doing things. Because there isn’t actually such a way. Eveything is possible and can be done with PHP (even not much approved). I do not truly know how the php’s source code is written, so if the separator causes a lot of trouble, maybe “” is not the best of choice, maybe people are right that this won’t be an issue for the current release but you are ruining the maintainability of the code with these. Maybe they are right. But that’s a balance issue more than anything. If you have so much performance problem, that write your code on assembly and you will get the best performace you can have.

I hope that this issue will be forgotten with the new release, but I don’t think so. Some people may even fork PHP and create a new language myPHP. I hope that won’t be the case. The decision is made, and your whining may not change this. What we should do, is to respect the decision and keep trying to improve PHP and if we really really want to change this, try to influence the decision for PHP 6 with facts. Do not talk about speculations but actual facts. I used this and that happened, if we had used this this would be better and else. But I think this can’t happen till new release.