Why PHP Was a Ghetto

Re:Why PHP Was a Ghetto by ch0wn on Tuesday April 19, 2011 @04:32PM (#2464091)

I came to say that. Even without comparison it should be very obvious that the PHP documentation is incomplete and badly written. The user comments can't make up for that, especially since there is no quality control for them.

The python documentation is an example of good documentation. And again, it's tied to the language's culture, where documentation has a really high priority.

[ Parent | on HN ]

Re:Why PHP Was a Ghetto by pavel_lishin on Tuesday April 19, 2011 @07:01PM (#2464584)

I don't know, I think the user comments add a great deal of valuable information - specifically, they're great examples of what you shouldn't do.

[ Parent | on HN ]

Re:Why PHP Was a Ghetto by seabee on Wednesday April 20, 2011 @01:54AM (#2465427)

They might be valuable, but I'd rather take a single solid, thought-out method over the reports of a hundred random, failed attempts.

[ Parent | on HN ]

Re:Why PHP Was a Ghetto by danik on Wednesday April 20, 2011 @05:02AM (#2465859)

The user comment on php.net consists mainly of bad advices with errors in the examples.

[ Parent | on HN ]

Re:Why PHP Was a Ghetto by eru on Tuesday April 19, 2011 @08:57PM (#2464826)

Yes, and even the Python documentation has lots of holes in them.

I'd often like a stronger emphasis on the types of arguments and what gets returned.

[ Parent | on HN ]

Re:Why PHP Was a Ghetto by hello_moto on Tuesday April 19, 2011 @11:15PM (#2465108)

Like um.... gasp Java?!

[ Parent | on HN ]

Re:Why PHP Was a Ghetto by eru on Wednesday April 20, 2011 @06:54AM (#2466071)

For example, if a furctions get a file, they should make it clear whether it's the name of a file or a File-like object. Or whether both are acceptable.

I don't know enough about Java documentation.

[ Parent | on HN ]