tealdeer-rs

tealdeer

Rust2018–2026

tealdeer-rs / tealdeer

tealdeer

A very fast implementation of tldr in Rust.

Explore on GitHub Read Hacker News discussions

14Distinct people

17Mentions

2Explicit recommenders

6.7KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

A very fast implementation of tldr in Rust.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I use tealdeer, which was my favorite of the few tldr clients I tried: https://github.com/tealdeer-rs/tealdeer Different tldr clients use different syntax highlighting, and…

wonger_ used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

tldr-pages/tldr · linked in 3 of the same discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year17 dated mentions

Observed mentions: 2018-02-13 15:32:23 UTC to 2026-02-20 13:11:30 UTC.

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	1	1	0
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	0	0	0
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	4	1	3
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	5	1	4
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	4	1	3
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	2	0	2
2024	2024-01-01 00:00:00 UTC	2025-01-01 00:00:00 UTC	0	0	0
2025	2025-01-01 00:00:00 UTC	2026-01-01 00:00:00 UTC	0	0	0
2026 (partial)	2026-01-01 00:00:00 UTC	2027-01-01 00:00:00 UTC	1	0	1

What Hacker News says

17 sources

wonger_·Feb 20, 2026Recommendation phrase

I use tealdeer, which was my favorite of the few tldr clients I tried: https://github.com/tealdeer-rs/tealdeer Different tldr clients use different syntax highlighting, and some are faster than others. The main tldr is horrifyingly slow iirc.

In Notes on Clarifying Man Pages

S04dKHzrKT·Jul 2, 2023

In Googling for answers costs time (2020)

doodlesdev·May 25, 2023

tldr pages are such a thing of beauty. I personally use the tealdeer [0] client though, since it's so much faster than the official client. [0]: https://github.com/dbrgn/tealdeer

In I didn’t learn Unix by reading all the manpages (2022)

seemaze·Jun 2, 2022

check out tealdeer, it's a rust implementation of tldr but improves speed (on my machine at least) drastically! https://github.com/dbrgn/tealdeer

In The Linux cheat command

thrtythreeforty·Jun 1, 2022Recommendation phrase

For even more brevity, there's tldr [1], which is short-n-sweet "how do I do the most common things with this tool." You'll need a client for it (tldr itself is just the database). I recommend tealdeer [2]. Example: $ tldr tar Archiving utility. Often combined with a compression method, such as gzip or bzip2. More information: <https://www.gnu.org/software/tar>. [c]reate an archive and write it to a [f]ile: tar cf target.tar file1 file2 file3 [c]reate a g[z]ipped archive and write it to a [f]ile: tar czf target.tar.gz file1 file2 file3 [1]: https://tldr.sh/ [2]: https://github.com/dbrgn/tealdeer

In Ffmpeg Buddy

bscphil·Apr 11, 2022

> While I find projects in those other languages to also have too many dependencies, it's no where near what happens in JS apps. I'm thinking of projects I've recently worked on in Rust, PHP, and Java. My experience with these new languages is such that this feels a bit unfair. It's like insisting that a disaster with 1000 fatalities is "much worse" than one with "only" 200. It's ... true ... I guess, but there's something uncomfortable about making the comparison. Something has gone badly wrong if the comparison even needs to happen in the first place. What I'm getting at is that e.g. Rust has an enormous problem in this area. It's not uncommon for me to see Node projects with over a thousand transitive dependencies, but on the other hand, I very frequently see Rust projects with over a hundred. And the Node projects tend to be more comp

Read the rest

licated than the Rust ones; they do more. Take the last Rust program I tried to use, tealdeer. [1] If you don't know, tldr is a project that provides alternative simplified man pages for commonly used programs that consist entirely of easy to understand examples for the program. [2] What a tldr client needs to do is simply to check a local cache for each lookup, and if necessary update the cache online. It's a trivial problem that can be, and has been! [3], solved in a few hundred lines of shell (if you're being extremely verbose). How many recursive dependencies would you guess tealdeer uses? Depends on how you count, of course, but as of today the answer is ~133 deduplicated dependencies! For a program that's a glorified wrapper around curl! Or another Rust program I looked at recently, rua [4]. In Arch Linux, the AUR is a repository of user maintained scripts for building and installing software as native Arch packages. Official tools for building and installing software already exist for Arch, but it is common for users to use a wrapper around these tools that makes fetching and updating the software from the AUR easier. It's a relatively simple task that (once again) can be done with shell scripts. rua is such a wrapper. As of today it uses 137 deduplicated dependencies! These Rust programs are simple terminal tools to do tasks that are almost trivial in nature. And yet they require hundreds of constantly updating dependencies! The situation may well be better than what you'll find for Node, but it's undeniably disastrous compared to either simpler languages without a built in package manager (like C) or more complicated batteries-included languages where best practices continue to prevail (like Python). [1] https://github.com/dbrgn/tealdeer [2] https://tldr.sh/ [3] https://github.com/raylee/tldr-sh-client/blob/main/tldr [4] https://github.com/vn971/rua

In Node.js packages don't deserve trust

dbrgn·Jan 1, 2022Submission

Tealdeer 1.5.0

2 points · Open discussion

dbrgn·Dec 31, 2021

I like Docopt for quick scripts, used it both in Python and Rust projects. It is quite unflexible though. The Rust Docopt implementation¹ was deprecated this year, which is probably good because clap v3² is so awesome. In a project of mine (tealdeer), I noticed that docopt.rs was responsible for the huge majority of CPU instructions when running the binary: https://github.com/dbrgn/tealdeer/issues/106#issuecomment-59... I then switched³ to clap and shaved off almost a megabyte from the release binary⁴. Performance improved as well, time required for rendering a tldr page went down from ~15.9 ms to ~12.4 ms⁵. With the migration, we also managed to reduce a lot of custom validation logic and move this logic into the derive macro attributes. ¹ https://github.com/docopt/docopt.rs ² https://github.com/clap-rs/clap ³ https://github.com/dbrgn/te

Read the rest

aldeer/pull/108 ⁴ https://github.com/dbrgn/tealdeer/pull/108#issuecomment-9448... ⁵ https://github.com/dbrgn/tealdeer/pull/108#issuecomment-9448...

In Docopt

throwamon·Nov 12, 2021

tldr is great! I personally use this faster implementation in Rust: https://github.com/dbrgn/tealdeer And I just became aware from reading the README that there's an even faster one written in Zig.

In Useful sed scripts and patterns

skyfaller·May 25, 2021

I think it's worth mentioning tldr as an effort towards more readable man pages: https://github.com/tldr-pages/tldr Personally I like tealdeer for a tldr client b/c it's written in Rust and I think the name is fun, but the other tldr clients I've tried all seem fine as well: https://github.com/dbrgn/tealdeer tldr doesn't do autocomplete, but between fish shell's autocomplete and tldr I feel I'm able to figure out most simple commands in the terminal.

In Launch HN: Fig (YC S20) – Autocomplete for the Terminal

samatman·Apr 9, 2021

I've switched to tealdeer: same database, rust implementation. https://github.com/dbrgn/tealdeer

In Why do long options start with two dashes? (2019)

jchook·Mar 29, 2021Submission

Tealdeer – A fast implementation of tldr in Rust

1 points · Open discussion

__henil·Dec 6, 2020Submission

Tealdeer: A fast implementation of tldr in Rust

2 points · Open discussion

ashton314·May 27, 2020

tldr [0] fills the missing piece you mention: good examples of common actions. (Though I use the Rust implementation tealdeer [1]) [0]: https://github.com/tldr-pages/tldr [1]: https://github.com/dbrgn/tealdeer

In CLIs are reified UIs (2017)

dbrgn·Jan 22, 2020

Regarding 1: Tealdeer provides static binaries for Linux. https://github.com/dbrgn/tealdeer/

In TLDR pages: Simplified, community-driven man pages

Showing the 15 most recent of 17 sources. Enable JavaScript to search and browse every indexed mention.