> The core of the PHP community is filled with a lot of really talented and smart developers doing some really amazing things.
Like those, who failed for years to actually consult the results of the test suite before shipping a new release? http://gcov.php.net/viewer.php?version=PHP_5_4
Like those who change stuff incompatibly to the worse, while introducing security holes?
http://php.net/manual/en/function.is-a.php
https://bugs.php.net/bug.php?id=55475
Like those were security fixes create even larger holes?
http://thexploit.com/secdev/critical-php-remote-vulnerabilit...
Like those who can't program a sane line of code in the language PHP is written in? "OMG, this calculation overflows, let's replace the int by an float!"
You can't make that shit up. I have nothing against stupid people, but against stupid people who fight against every kind of process who could prevent their own stupidity like
- "learning from mistakes",
- "learning the language they actually program in",
- "handling bug reports in a way it doesn't alienate reporters" or
- "having a decent test coverage".
Instead of thinking about yet-another-documentation site, what about fixing the devastating quality of their API documentation (especially the comments)?
Like those, who failed for years to actually consult the results of the test suite before shipping a new release? http://gcov.php.net/viewer.php?version=PHP_5_4
Like those who change stuff incompatibly to the worse, while introducing security holes? http://php.net/manual/en/function.is-a.php https://bugs.php.net/bug.php?id=55475
Like those were security fixes create even larger holes? http://thexploit.com/secdev/critical-php-remote-vulnerabilit...
Like those who can't program a sane line of code in the language PHP is written in? "OMG, this calculation overflows, let's replace the int by an float!"
You can't make that shit up. I have nothing against stupid people, but against stupid people who fight against every kind of process who could prevent their own stupidity like
- "learning from mistakes",
- "learning the language they actually program in",
- "handling bug reports in a way it doesn't alienate reporters" or
- "having a decent test coverage".
Instead of thinking about yet-another-documentation site, what about fixing the devastating quality of their API documentation (especially the comments)?