>>120
Don't forget everyone that these errors come because of people enforcing unrecommended settings and being sucky programmers. Perhaps PHP's problem is it has kind of an exponential learning curve; it's very easy to start using it, but it's also very easy to do it all wrong. There are some functions you shouldn't use, and ways of doing stuff which are far better than others, but noobs don't realize this and this is why a lot of PHP code sucks. This is why it's being overly bashed in some scenes. But there ARE good PHP programmers out there. And once you get it right, you can be very productive with it, and it has a cleaner syntax, which matters to me.
>>122
Well, that depends on what are you doing with it. I'm a productivity person if we're talking web applications, database applications, and scripts. I'm a shit sux fag use C guy when we're talking games, or applications that deal with massive amounts of data (typically, 2D, 3D and sound). Don't forget 80%-90% of the software anybody currently has in his/her hard disk is written in C/C++/C++--.