Yes, that's rather the parent's point, I think.

except "many of the frameworks that exist for it hide or transform enough of the "native" implementation details as to be different languages. Or supersets of it" is wrong. It's all still javascript. Just.. plain.. javascript. with a different api/library.

I don't think you understood what I wrote. And I'll leave it at that.

is there an alternative interpretation? you appear to be saying that a library can make javascript into a new or superset language.

Are you saying something different?