Your skill will accomplish what the force of many cannot |
|
PerlMonks |
Re^5: The REAL reason for why they choose PHP over Perl.by exussum0 (Vicar) |
on Jun 15, 2006 at 15:53 UTC ( [id://555530]=note: print w/replies, xml ) | Need Help?? |
You've ignored something I've said. perl is more than just mason. If you wish to do database work, you have DBI and tonnes of DBDs you can install. You have Class::DBI and many other forms of data access. You have modules for PDF, Word. Mason doesn't support it outright, where php directly does.
In php-land, some large portion "modules" are actually c extension for php. In php, you have the mysql_*, postgresql_* and the direct db functions and that's about it. Yes, pear is an abstraction layer, but nothing beyond abstraction has been done yet. perl has various forms of data access as i've stated before. In perl, modules go into a namespace with a PERL5LIB path. Most of your code is written IN perl. In php, you are limited to includes which don't use a lib path where most of your modules are written in c. You can't write a multithreaded php application. And there are differences between php and mason post installation. To add modules is completely different between the languages. php is a web language first, and a programming language second. perl is a programming language first, and a web technology second. the internals and the language design lead toward this. I could go on and on. but please, stop ignoring that this is perl vs php, not mason vs php. Mason is cute, and it mimics php.
In Section
Meditations
|
|