One could argue that "cool new things" being never written in perl _is_ a ~marketing~ problem.
I think the GP was actually trying to say that the traction is missing for an otherwise nice and mature/stable infrastructure. A couple of "shiny" projects that boldly host with a powered by perl on their page might bring in fresh blood..
One could equally argue that not jumping on new concepts until they've been demonstrated to have real world value is an advantage.
As a community, we tend to like to really think about things before implementing them - which means that while new ideas might turn up in perl a bit later than in other places, they tend to turn up in a well thought out way that we can confidently maintain backwards compatibility with over time.
When you're writing code that may still be in production in five or ten years, this tends to be an advantage.
I think the GP was actually trying to say that the traction is missing for an otherwise nice and mature/stable infrastructure. A couple of "shiny" projects that boldly host with a powered by perl on their page might bring in fresh blood..