why typescript and not go

[samarth-na]

not much else to ask really

[ryanjsalva]

We wanted to...

1. Make it easy to contribute. JS (63%) and TS (38%) are consistently among the top 5 most used languages, making them accessible to an outsized portion of the community.
2. Leverage the ecosystem. There were some excellent tools already available in the JS/TS community that allowed us to iterate quickly (e.g. Ink).
3. Build something portable. JS/TS is probably one of most portable technologies. It's easy to run everywhere.
4. Work with something familiar. The team is pretty small, and TS was a familiar language. We optimized for moving fast.

Honestly, a CLI in Rust or Go would be fantastic. Who knows? Maybe we'll do it all over again. 😉

[loadingalias]

Why not Rust? Don't you feel like you're leaving stable perf updates on the table? We could be using ripgrep instead of grep; fd instead of find; eza instead of ls.

We'd have much higher performance and less weight.

I can't understand the choice outside of access to Ink... which is great for beautiful CLI... but is a bowl of spaghetti to read.

edit
I'm sorry I'm lazy and didn't read your response first. FML - embarrassing.

[allenhutchison]

We aren't precluded from running the faster rust based tools. In fact we were talking about this in a team chat yesterday with the idea of looking for those alternatives on the system and if they exist using them instead of the slower more widely available versions.

[zessu]

You seem some people ask for a Rust or Go rewrite, you go to their profiles, they don't even contribute to anything lol