"D" dsc@clara.net writes:
PHP/MySQL one of the best combinations for any website!
PHP is bad because... * Encourages mixing of code, layout and content * It has an object system but no-one uses it * It has all the security problems given in the "study in scarlet" doc
MySQL is bad because... * It encourages use of lots of non-standard SQL extensions * It doesn't crash neatly (full disks are sometimes fun) * Its performance for non-trivial operations is often suboptimal
Why do I fell like dropping chaff now?
On 05-Aug-01 MJ Ray wrote:
"D" dsc@clara.net writes:
PHP/MySQL one of the best combinations for any website!
PHP is bad because...
- Encourages mixing of code, layout and content
But that is its whole rasion d'etre. As it is for TTK and mason.
- It has an object system but no-one uses it
You clearly mix in the werong company. Mix with quality design and implementation teams and you will find that the object system is used, and used consistently and extensively.
- It has all the security problems given in the "study in scarlet" doc
It is quite possible to write bad PHP, as well as bad perl or C/C++. It is also possible to write good PHP.
All that said, I do not like PHP; I much prefer perl. The main problems I have with PHP are that it does not provide me with the ease of string handling that perl does, and I find the language syntax just a bit clumsy - a bit too reminiscent of Fortran.
-
MJ Ray -
Raphael Mankin