See github's bad language detection if I put jquery in git. Well, actually, no [0]. Just use the standard name and Linguist ignores it. But your larger point

See github's bad language detection if I put jquery in git. Well, actually, no [0]. Just use the standard name and Linguist ignores it. But your larger point is still valid: popularity does not imply utility. Unless I'm assuming I'll use the exact same employees for both You really should be. If your devs only understand a siloed part of your codebase you're doing it wrong. that they only know JS and that they're so worthless they can't pick up a second language Holy private demons, Batman! I don't know how you've been hurt in the past but please don't bring it here. There are plenty of valid reasons to intentionally avoid introducing a second language on a project. In fact, I'd argue that the burden of proof is on showing why it's worth introducing the additional complexity. [0]: https://github.com/github/linguist/blob/master/lib/linguist/vendor.yml#L56 https://github.com/github/linguist/blob/master/lib/linguist/...