"If `BigNameCorp` writes a lot of PHP seriously, you won't notice that many problems."
It also depends on how long BigNameCorp has been around. They might take coding seriously now, but legacy code in general is a pain to deal with. Much less legacy code that's been written in a language like PHP.
Array dereferencing in is the trunk and will be available in 5.4.
Re:Ask HN: PHP for Python programmers
by damncabbage on Sunday September 12, 2010 @07:36AM
(#1683476)
And will be available for use on BigNameCorp's RHEL servers in about eight years.
If you do however see an old-style "let's just include everything", "global variables are cool", "just shove it into $_SESSION" kind of code... well - good luck, you'll need it ;)
There's also going to be some forehead slapping as you discover what is not possible (like `function_returning_array()[0]` => syntax error)
I get to write PHP once in a while but normally prefer Python. It's easy to spot in the style of the code written... but otherwise, no problems. I'd just suggest changing the error reporting level to maximum - it's not hard to write a lot of PHP code that will both work correctly and report tens of warnings per line.