I like Javascript... but it is certainly an unholy amalgamation of mismatched parts that, in the end, can get pretty much anything done if you don't mind 100+ node dependencies.
Probably more importantly, it runs on the JVM and is designed to interoperate with existing Java code. (FWIW, I actually think they made a major mistake in how they handle null Java objects, and that Kotlin did better here; but Kotlin is much newer.)
My experience in going from C to C++ was different: if you're not converting everything from mallocs with custom addressing systems to the collections framework, you're not living.
My experience with C++ was when C++ was a relatively new thing. Practically the only notable feature provided by the standard library, was that unholy abuse of bit shift operators for I/O. No standard collections or any other data types.
And every compiler would consider something else a valid C++ code or interpret the same code differently.
I am little bit prejudiced since then… and that is probably where the author is coming from too.
Then things were just getting more complicated (templates and other new syntax quirks), to fill the holes in attempts to make C a 'high level language'.
Java is extremely widespread in corporate companies - hence the suit and tie. Perl is fair to liken to spelunking deep into a dark cave with only your wits to save you.
PHP seems to be a reference to the fact that it's extremely common on servers... but it also might be a lazy phpbad joke - it's pretty weak either way (if you wanted to play into the server characteristic give it a dozen arms serving the entire restaurant in the background).
As a Perl dev, I dunno if that's how I'd characterize the language, but I'll take it over yet another "Perl is unreadable line noise lol and what's the deal with airline food" reference.