News for hackers. Stuff that matters.
Re:Google App Engine finally supports PHP by Kiro on Saturday May 18, 2013 @11:26AM (#5729221)
I am no hardcore programmer and PHP is perfect for me. Tbh I haven't encountered one single bad thing about it during my 5 years programming, although I understand there are major flaws in it. What I'm saying is that for most people PHP works completely fine and is as good as anything.
Re:Google App Engine finally supports PHP by sethrin on Saturday May 18, 2013 @12:24PM (#5729439)
This is true. But it's HN so if you say that, you have to dress it up a bit, throw in some jargon and name-drop some computer scientists -- "Turing-complete" counts for both categories, and is even somewhat relevant to the topic.

It's also not true. "Infinite are the arguments of sages," I hear, or something to that effect, but the distinguishing mark of expertise is not being able to offer an unqualified endorsement of any position.

The element of your comment that I find most concerning is that, after five years of using a programming language, I feel that you should be aware of its major flaws. Probably the minor flaws too. You should be aware of how it differs from other equivalent tools. And, if you don't know that, then the content of your post should not be "PHP is good," but "Why is PHP considered to be bad?"

Re:Google App Engine finally supports PHP by Kiro on Saturday May 18, 2013 @12:33PM (#5729465)
I do know the major flaws, it's just that they have never been a problem when I code stuff. I don't find myself thinking "oh, PHP is so bad" or that I can't do what I want because the language is flawed. I've used RoR, Django, Node.js but for the stuff I do (as I said, I'm no hardcore programmer) PHP simply works better or at least as good for me.
Re:Google App Engine finally supports PHP by danbruc on Saturday May 18, 2013 @12:03PM (#5729336)
Of course, you can build working stuff with PHP. It is good enough for weekend projects and prototyping stuff. Companies like Facebook have even proved that you can build huge things with it.

Put that's not the point. It's not about bashing PHP for the sake of it. A large number of software projects is behind schedule and over budget. Why? Because developing software is hard and humans are bad at estimating effort.

Now why should we make the situation even worse by using tools that are not as good as possible while we are completely aware of the flaws (and good things) in our current tools?

Pointing out PHP's flaws over and over again while seeing that its usage does not drop tells us something - there seems to be no (obvious) better alternative. »PHP sucks!« is crying for help. Someone please build an obviously better alternative. Ideally as compatible as possible to make porting from PHP not practically infeasible.

Re:Google App Engine finally supports PHP by pornel on Saturday May 18, 2013 @03:30PM (#5730055)
Most PHP flaws that people moan about are shallow. Inconsistent naming of functions and parameter order, syntax warts — those are annoying, but ultimately don't matter.

What matters is that PHP has got big things right. Deployment is trivial. One process per request happens to mitigate leaks and (over)shared state. Failures affect one client at most, and scalability bottleneck is pushed down to the database.

Re:Google App Engine finally supports PHP by Kiro on Saturday May 18, 2013 @12:38PM (#5729485)
I would still say that for most people these flaws are no game-changer. We simply don't code stuff advanced enough for it to matter.
Re:Google App Engine finally supports PHP by sbarre on Saturday May 18, 2013 @03:43PM (#5730112)
> A large number of software projects is behind schedule and over budget. Why? Because developing software is hard and humans are bad at estimating effort. Now why should we make the situation even worse by using tools that are not as good as possible while we are completely aware of the flaws (and good things) in our current tools?

The above has much less to do with PHP and more to do with the lack of experience of the developers, I would say..

"Tools as good as possible" is an extremely subjective thing, and there is no magical tool or framework that works perfectly in all hands.

Developers should choose the tools that are best suited to the job at hand, and "best suited" doesn't just mean the functionality and features, it also encompasses developer proficiency.