Me neither (and I only really have 'it's basically the same as [take your pick]' level familiarity with JS/TS anyway) but I bet my manager planning the hypothetical multi-platform project would be. It means it's either greenfield or a re-write. It probably affects hiring even if I think we'd agree it shouldn't.
And it's not just 'learning' it, the language itself, it's library availability and the general ecosystem. Which is obviously a bit of a chicken-and-egg problem or tautological even that '~nobody wants to use it because ~nobody uses it'.
> And it's not just 'learning' it, the language itself, it's library availability and the general ecosystem.
Exactly, there’s a whole universe in a bottle that comes with each language, and I think that is what is the largest source of friction these days when developers consider using a language, especially when the language has little to nothing unique to offer in exchange.
And it's not just 'learning' it, the language itself, it's library availability and the general ecosystem. Which is obviously a bit of a chicken-and-egg problem or tautological even that '~nobody wants to use it because ~nobody uses it'.