It may just be a strong bias against PHP.
But even if we did choose to rewrite at some point, how do you choose?
Java is "enterprise-y" and people generally hate it.
As you mention, Ruby has fallen out of fashion, and it's always had a reputation for being a resource hog.
Python is a great language overall, but was never really meant for web programming so ends up being a bit kludgy.
Node is super popular with the bleeding edge crowd, but it's only been around for 3 years and speaking of wooden bullets -- Javascript has more language pitfalls than PHP! And there's still no clear winner in terms of framework stack.
Meanwhile, Google has invented its own proprietary languages , which seems like a real Microsoft in the 1990s kind of move.
So even if we started over, it's pretty unclear what we'd choose to build with.
I'd pack my bags tomorrow for a Lisp job.
That said, my own coding is currently leaning toward Node.js for server stuff. I'm using Neo4j for data and it turns problems right on their ear - for my space (not all spaces), it's a million times better than relational and a thousand times better than document databases. So I'm looking for languages/frameworks that make my particular use of Neo4j more graceful. Started with Rails, but gave it up as the ActiveRecord ORM is kind of Neo4j-hostile in practice. I expect this is true of most ORM solutions (hence the R, for "relational"), so maybe I can make it better in a lighter-weight system.
At any rate, there are no silver bullets, but plenty of wooden ones. I lump PHP in that category. If there's an existing PHP app, then by all means maintain it, but don't use it for new projects!