TalkPHP - View Single Post

Wildhoney · 10-01-2007, 12:00 AM

I was reading the following article yesterday. In admission it is a banal article with 2 interesting points, 1 is how PHP looked right at the beginning, and secondly, how PHP got in such a mess with its functioning naming - such as the mixture of function naming conventions, like str_replace and strpos.

I couldn't help but feel that the explanation the founder of PHP gave in that article was a mere cop out. The reason it got in such way, to me, is down to little to no planning. That's the mess you get in when you don't have clear instructions on what you're doing. You just keep adding things randomly when you need it.

See what you think. The segment is headed The Ugly Duckling of Programming Languages. Towards the end of the paragraph he goes onto mention something about sometimes you need an ugly solution to an ugly problem. I disagree. I think there's absolutely no need to have an ugly solution when you could have a pretty solution with a well-managed and properly planned out project. There is no excuse, in my eyes.

The solution for me is PHP should break all ties (thus sacrificing backwards computability) with the previous versions and risk breaking a lot of scripts when they upgrade their PHP. This, however, I feel, will never happen as people may begin to turn to other languages such as Ruby and Python instead of sticking with a language that has just turned their site on its head.

This is the greatest reason why PHP will continue to be added to and not thought out properly. I admire their revamp of OOP in PHP5, but the previous suggestion would be too big of a risk. With every passing day the decision to do this becomes more difficult.

Your thoughts?

10-01-2007, 12:00 AM	#1 (permalink)
Wildhoney La Vida es Sueño Join Date: Sep 2007 Location: Oldham Posts: 2,280 Thanks: 90	The reason for PHP's lack of protocol I was reading the following article yesterday. In admission it is a banal article with 2 interesting points, 1 is how PHP looked right at the beginning, and secondly, how PHP got in such a mess with its functioning naming - such as the mixture of function naming conventions, like `str_replace` and `strpos`. I couldn't help but feel that the explanation the founder of PHP gave in that article was a mere cop out. The reason it got in such way, to me, is down to little to no planning. That's the mess you get in when you don't have clear instructions on what you're doing. You just keep adding things randomly when you need it. See what you think. The segment is headed The Ugly Duckling of Programming Languages. Towards the end of the paragraph he goes onto mention something about sometimes you need an ugly solution to an ugly problem. I disagree. I think there's absolutely no need to have an ugly solution when you could have a pretty solution with a well-managed and properly planned out project. There is no excuse, in my eyes. The solution for me is PHP should break all ties (thus sacrificing backwards computability) with the previous versions and risk breaking a lot of scripts when they upgrade their PHP. This, however, I feel, will never happen as people may begin to turn to other languages such as Ruby and Python instead of sticking with a language that has just turned their site on its head. This is the greatest reason why PHP will continue to be added to and not thought out properly. I admire their revamp of OOP in PHP5, but the previous suggestion would be too big of a risk. With every passing day the decision to do this becomes more difficult. Your thoughts? __________________ The man who comes back through the Door in the Wall will never be quite the same as the man who went out.