3 ms·

> it's quite plausible that TS is one of only a small number of languages that you know that all your co-workers will be proficient in. If by TS you mean Javas

> it's quite plausible that TS is one of only a small number of languages that you know that all your co-workers will be proficient in. If by TS you mean Javascript with ": any" tacked onto the end of each variable, then perhaps. Actual TS proficiency is rare, in my experience. But if proficiency is a concern, you're not going to slap any random web developer on a command line tool project. It is an entirely different skillset. Amongst the developers proficient in command line tools, I expect the common language they are familiar with is typically not TS.

Capricorn2481 3y ago
> If by TS you mean Javascript with ": any" tacked onto the end of each variable, then perhaps. Actual TS proficiency is rare, in my experience. This isn't even a lack of proficiency, this is just hiring bad people. Who doesn't know how to annotate a type? That hardly takes Typescript "proficiency," you can learn it in 5 minutes.
- randomdata 3y ago
  > 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.
andrewaylett 3y ago
If our hypothetical web developer needs a command-line tool, why shouldn't they write it themselves? And why would using different programming languages be the same skill-set, but CLIs vs GUIs be a different skill-set? There are other considerations to take into account, too: in an environment that commonly uses `npm`, a JS or TS package may be the easiest way to distribute your CLI tool. Especially if it's a tool intended to be used in the context of an NPM-based project. For what it's worth, I have published CLI tools: `downgrade-build` is written in TypeScript, published with NPM, and used by my other NPM packages. `dabl` is written in Rust, published on crates.io, and honestly will probably only ever be used by me but it's useful to me :).

Capricorn2481 3y ago

> If by TS you mean Javascript with ": any" tacked onto the end of each variable, then perhaps. Actual TS proficiency is rare, in my experience. This isn't even a lack of proficiency, this is just hiring bad people. Who doesn't know how to annotate a type? That hardly takes Typescript "proficiency," you can learn it in 5 minutes.

randomdata 3y ago
> 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.

andrewaylett 3y ago

If our hypothetical web developer needs a command-line tool, why shouldn't they write it themselves? And why would using different programming languages be the same skill-set, but CLIs vs GUIs be a different skill-set? There are other considerations to take into account, too: in an environment that commonly uses `npm`, a JS or TS package may be the easiest way to distribute your CLI tool. Especially if it's a tool intended to be used in the context of an NPM-based project. For what it's worth, I have published CLI tools: `downgrade-build` is written in TypeScript, published with NPM, and used by my other NPM packages. `dabl` is written in Rust, published on crates.io, and honestly will probably only ever be used by me but it's useful to me :).