I think, from my experience at least, that we keep getting these "component reuse" things coming around "oh you can use Company X's schema to validate your XML!" "oh you can use Company X's custom web components in your web site!" etc etc yet it rarely if ever seems to be used. It very very rarely ever feels like components/schemas/etc can be reused outside of their intended original use cases, and if they can they are either so trivially simple it's hardly worth the effort, or they are so verbose and cumbersome and abstracted trying to be all things to all people then it is a real pain to work with. (And for the avoidance of doubt I don't mean things like tailwind et Al here)
I'm not sure who keeps dreaming these things up with this "component reuse" mentality but I assume they are in "enterprise" realms where looking busy and selling consulting is more important than delivering working software that just uses JSON :)
There are many people who think of themselves as a “X programmer” (and perhaps Y and Z), and managers/companies looking for them.
Then there are people who think of themselves as software engineers, and the language does not really matter (and companies that hire for that).
If often see the two camps talking past each other.
On the other hand, Pascal was my “introductory” programming language (I already knew BASIC pretty well at that point), but it certainly wasn’t the only one in my program - we did Perl, Prologue, C, C++, etc.
In a professional software development career, it certainly won’t be the last language you’ll learn.
Too bad. News broadcasts are full of those ads, and hence TV journalists are loath to investigate the people that pay their salaries.