Both of these things can be rectified by some gymnastics or call_user_func_array (very slow), but it's something that I could do in JavaScript or C# or almost any other language if I wanted to, but not PHP.
It drives me crazy, and almost every day there are one of these things. I never have to say "I wish JavaScript did $x," unless there's a library I need that I don't have. On the other hand, in PHP there has never been a time that I've had to say "Oh, there's no library for this."
It's a game of tradeoffs, and, for me, bitching about syntax is greatly preferable to having to port a library to another language or start from scratch.
To build an extra robust tool you need a lot of planning, and a lot of factors are considered during the planning.
I write absurd amount of code and I truly do not start crying because I'm using PHP, JS, or something else. I run into style issues, for instance, in PHP I might use is_num instead of typeof foo === "integer" like in javascript.
When I have a problem with a tool I'm using, it's more like "Arg, the API for new modules in angular is too close to the API for calling already created modules!!" not, "Oh no, jQuery is bad because Backbone is bad, because backbone is written in JavaScript, and you can do some mighty awful things in JavaScript!"
If you're crying about things on the language level, you're not building robust systems.