> This isn't even a lack of proficiency, this is just hiring bad people. If there was some specific reason to hire Typescript developers, maybe. But across an

> This isn't even a lack of proficiency, this is just hiring bad people. If there was some specific reason to hire Typescript developers, maybe. But across an organization, many developers won't be working on Typescript projects and there would be no reason to hire based on Typescript ability for those projects. It may be one of the few language all developers have some familiarity with, as proposed earlier, but that doesn't mean it is the language all developers focus on. And when hiring developers with a background in building command line tooling, it is likely that Typescript has never been a language that has garnered their attention. > Who doesn't know how to annotate a type? That hardly takes Typescript "proficiency," you can learn it in 5 minutes. Typescript is its own language – one that is even turing complete. While you likely can learn it in 5 minutes, same goes for any language, including the aforementioned Go, Rust, and Zig. Proficiency takes quite a lot longer, though.