And again, evidently, you've got no idea what proper meta-languages are (i.e., featuring a static compile-time metaprograming with a full, again, compile-time reflection). And yes, I'm perfectly aware of the fact that even majority of Lisp users got no clue how to use metaprogramming properly.
> You say it like you mean it, which means you don't understand the importance of syntax, semantics, type systems, and several more concerns
Obviously you do not understand metaprogramming. I do not care at all about syntax, semantics, type systems and all that of a host meta-language. I can build any combination of this stuff on top, easily. Of course as long as the host language is not trying hard to break things - this is what separate a proper metalanguage from an inferior one.
> (not to mention pragmatic issues like ecosystem and tooling).
Again, you do not understand metaprogramming at all. Once you start parasiting on any given language you're getting all of its ecosystem and tooling in, for free.
> You also yield "metalanguage" like its conventional CS wisdom that being a metalanguage is some magic bullet trait, that makes it "superior simply by definition".
I gave a definition, if you did not notice. A meta-language is the one which can be turned into any possible language, statically.
> which would also include things like Antlr, m4, PEG, transpiler generators, and such, for which there's nothing "superior" to a conventional language.
I gave my definition, which (conveniently) fits Lisp in.
> Not sure were you picked the terminology up, probably some book or article, but it doesn't mean what you think it means
Not sure you know it better.