Octavian Rasnita wrote:
Hmm, sorry. I was just trying to think to something that might make perl
more used than PHP.
- PHP is crap and a half to admin
- Its huge and clunky
- PHP based systems are more prone attack since PHP relies to much oin
assumptions ("Oh its quoting it all for me, so I can do SQL and system
commends without checking" so says the coder you mention below :))
The scope of advocacy is not to make perl better, but to make it be used by
more programmers, and most programmers are not super programmers which are
able to create an operating system, but just coders that like a language
which is easy to learn, use and maintain.
I don't know why some people are so angry when showing them that perl has
many disadvantages. If the disadvantages are shown, they can be seen and
fixed.
Another difference:
"disadvantages" shown for any language can burn the ego a bit :)
realistically though PHP has waaaaaay more disadvnatages.
For instance if you try to secure your php.ini by dusabling functions,
doing safe mode etc etc and you want PHP to run as the user so you use
PHPSuExec like a good lad the evil user goes touch ~/public_html/php.ini
and *poof* your php.ini is overridden and they can turn off anything
they like. This is not considered a bug but a feature!! Which makes sens
because that allows the user to define custom settings like .htaccess
does *but* you can override 100% anything and the documentation on how
to limit it buried deep in some PHP luser's underwear.
PHP is cute and all but in a perfect world it'd be nonexistant. I'mnot
just saying that Pelr is the best, use *anything* you like Python, Ruby,
C, whatever just so its not PHP :)
When I look over job applications and I see PHP experience I immediatley
think "NEXT" because PHP's paradigm results in cluseless coders and
clueless coders = bad security + lots of other things...
