Why do you disagree?

A side thing would be that do people meaningfully install from pip or npm directly for tldr, or do they mostly rely on their OS' package manager, and that the majority of end users really don't care what language the client is written in, they just want that it functions, it updates with their other OS packages, etc.

"We", the tldr-pages organization, do not have an official client for the browser or Android. Perhaps there's interest in making one (cool), but on that same vein, there should only be one official browser client, one official android client, alongside the one CLI client.

We do have an official client for Android, that is the Python client with the official install method pip, I use the same in Termux and it works fine. I don't think a seperate repackaged one is necessary (maybe I will highlight this is Python client README, Clients Wiki).

Regarding, the browser client currently there is only one official client, the previous one has been archived. So I don't get the argument.

While, outfieldr and tealdeer are packaged natively. Termux suggests packaging applications for pip (and they won't accept it into their native repos if it is already packaged for pip, the other two community clients aren't written in Python, that's why they are packaged in the repo natively).

While you can install NPM client too, it has broken rendering in some places and isn't good on phone with the indexing after fetching archive. Also, Node versions aren't the recent one in their repos and often lacks security updates.

Ref image of Python client

Ideally, there'd be a strong link between making spec updates to the client updates. Given the worry about people coming and going, you'd ideally also chose a language that you would have a more broad appeal that would ideally always have a tldr-pages maintainer that works in that language. Like, while I think elixir is a cool language, I don't think it's a great fit given its relatively niche usage (atm). The client also shouldn't be that complex that I think it'd be hard for someone to pick up while learning a new language if need be.

I agree that elixir is a complex language and we barely have any other contributors, I would suggest retransferring extldr repo back to @ivanhercaz (and they can continue developement from there at their own pace) instead of archiving it in Org. If you notice, I still haven't updated it's status in Wiki from archived and that's intentional.

Regarding, tlrc I believe Rust is far more common and accessible to pick up for existing maintainers and new contributions.

I would suggest retransferring extldr repo back to @ivanhercaz (and they can continue developement from there at their own pace) instead of archiving it in Org.

As I commented in Matrix, I am just trying to return to the project, maybe writting some pages, maybe translating. Refactoring of extldr and compliance with the official clients spec is something that will happen, but I can't promise when and any deadline because at this moment it isn't a top priority for me.

But yes, instead of archiving it, please, transfer back to me, please.

How would one pip install on Android without a terminal being supplied by default?

How would one pip install on Android without a terminal being supplied by default?

Currently, it's only possible to do this using Termux, but Android 16 is getting native Linux terminal support (first rolling out to first party devices like Pixels), so this should hopefully work by default in the future (by enabling Linux development environment from settings).

We can probably add a note/instructions to the Python client repo on how to run it on Android.

Hi, thanks for expressing your opinion. As mentioned above, we don't intend to drop any of the currently active official clients as each of them are required for cross platform compatibility and serve unique purposes.

If you are in Windows, you can either install our Rust client using winget at winget install tldr or if you have NPM then npm install -g tldr. I am not sure why you aren't sure about choosing a client, while winget package isn't well known, we advertise the Node client as the primary official one in README.

Regardless of the client you use the base features are same. You can also use tldr without a client on the web using services like https://tldr.inbrowser.app, https://cheat.sh and https://command-not-found.com. If platform specific ones aren't for you, for commands you can directly check the markdown pages on the repo or through any web client/service.

Thank you so much @kbdharun! I do use Windows, so I'll be sure to look into these options next time I'm on that machine. However, the above feedback was written from the context of trying to use this on a Mac.

I generally install things with the heuristic of "if it can be installed using my system's package manager, go that route"; I like to manage my packages in one place, so I try to avoid npm install -g when possible.

So from that perspective, the README used to advise brew install tldr which installs the C client. Now the README's been updated to recommend the Rust client instead, even though the C one is still available too. And neither of these is the primary official one (Node)!

Based on your above response, it sounds like the Rust client should be "good enough" for my needs. But I do think newcomers on macOS might be confused as to why they shouldn't be accessing "tldr" using a package named tldr.

Python and Rust clients are actively maintained and are packaged for many distros(python - Fedora, opensuse - Rust)