News for hackers. Stuff that matters.
Re:Inconvenient Truths about TypeScript by Hermitian909 on Tuesday July 18, 2023 @10:37AM (#36773090)
Even if they know better suited languages, do they know the same better suited languages?

I'm in a TS shop, 95% of our code is TS. I would assume that almost everyone we've hired knows at least one compiled language but that language might be C++, Go, or Java. The only way to write a CLI tool that anyone at the company can edit is to write it in TS and so, indeed, >90% of the CLI tools we write are in TS. Works fine.

Re:Inconvenient Truths about TypeScript by randomdata on Wednesday July 19, 2023 @09:41AM (#36786175)
> The only way to write a CLI tool that anyone at the company can edit is to write it in TS

The only way? If you know C++, Java, or Go, even Typescript for that matter, they are all almost exactly the same. There is a little nuance with respect to setting up a project idiomatically, but once that groundwork is laid anyone can come along as they're simply going to copy the structure and style of what is already there anyway.

Re:Inconvenient Truths about TypeScript by Hermitian909 on Thursday July 20, 2023 @11:10PM (#36809567)
> There is a little nuance with respect to setting up a project idiomatically, but once that groundwork is laid anyone can come along as they're simply going to copy the structure and style of what is already there anyway.

You might think so! Having seen this tried in multiple 100+ engineering orgs, I think empirical evidence is against you. CLI tools can get surprisingly complicated (or use a surprisingly complicated set of language features). Many engineers will simply give up if a solution is not obvious in the first 5 minutes.

The end result is you have a lot of team A asking team B for a minor feature or fix to team B's CLI tool, or worse, team A just writes a hacky workaround to the broken-ness in the CLI tool.

Most people just don't care enough to put in the kind of effort for anything but the easy path.