Comments on: Reason #283 why PHP is less productive than Perl

By: simplem

simplem — Wed, 03 Dec 2008 20:40:09 +0000

@Josh – Although PHP seems to have borrowed a lot of perl-like concepts, you can’t lump them together at all. I think you would be slightly impressed by Perl’s design if you took an objective look at it.

By: Abhi

Abhi — Tue, 11 Nov 2008 05:13:09 +0000

@Baron
Do you replicate the request parameters by passing them while invoking the script from the command line?

By: moto

moto — Sat, 08 Nov 2008 03:44:35 +0000

debug_print_backtrace();
http://us.php.net/manual/en/function.debug-backtrace.php

By: Xaprb

Xaprb — Fri, 07 Nov 2008 17:19:05 +0000

Josh, that’s reason #282 why PHP is less productive. As such, it is strictly off-topic in this post. Just kidding ;-)

I totally agree with you there — it’s like someone took playing cards representing every function in every C library and shuffled them together. And the result is a very dog-eared namespace.

By: Josh

Josh — Fri, 07 Nov 2008 17:12:07 +0000

@fenway:
Not really look at function list for functions beginning with the letter A:
http://www.php.net/manual/en/indexes.php

PHP designers didn’t seem to care about discoverability or usability of the language and namespacing.

Sure you can write good or bad code in any language. Just some are better designed and a joy to use. Others should be sucumbed to better technologies.

PHP and Perl do not sit on my list of well designed languages. I prefer to spend my time in languages that seem to be progressing forward not stuck in the 80s.

They are still around because the amount of legacy code has reached critical mass early.