Seriously! According to the time command in fish, cldr (my program) takes around 4-5 ms to print files, tldr takes 80-100ms. (PS, on my server, cldr actually takes less than 1 ms to fetch the file, while tldr takes closer to 150 ms. That’s 150 times faster!!!)
This started a couple days ago when a friend of mine alerted me to the fact that the official tldr repo now takes ai contributions for their pages (aka the cheat sheet files that are printed) and for the actual program code. She then showed me a repo called ethical-tldr which does not allow for the use of ai contributions in the pages or program code.
However, their even though their client doesn’t allow vibe coding, it is still written in Python, which itself takes ai contributions.
So, I decided to learn C from scratch and make my own tldr client that’s faster and better than theirs in *every way! Introducing cldr! I am especially proud of the list and search functionality because the interface is just gorgeous.
Note, ABSOLUTELY NO AI was used in the making of this, I learned and wrote everything on my own in just the past 3 days, I don’t think I even copied much or any code from websites.
*There’s still like two things I haven’t implemented that the official client does, but they’re very minor and I’d be willing to bet that 99% of you won’t know the difference.


What your project desperately needs is a description of what it does. I had to follow the links to ethical-tldr back to the original tldr to see what it’s supposed to do.
Ohh! That’s a good point! Thanks! I just updated the README to provide an actual description.
deleted by creator

I could only wish to be this cool.
This is an instance of that recurring trope of coding something better out of pure spite
https://github.com/tealdeer-rs/tealdeer Rust TLDR
So… C code is faster than python. We knew that. Thanks for the better performing rewrite. Now do it in rust 🤓
Looks like someone did that https://github.com/tldr-pages/tlrc
There’s also https://github.com/tealdeer-rs/tealdeer
In all distros I’ve recently used this is what gets installed when you install the “tldr” package with the package manager. And for good reason.
I’ll admit I have no idea what makes one of the Rust implementations preferable over the other. Nor can I go looking at the code myself now that GitHub has hosed itself again
Why in rust? I mean it would be less faster, right? If speed is of the essence ofc.

This looks like a colossally bad idea:
if (!strcmp(platform, "windows") && !isSpecificPlatform) { debugLog("Falling back to rm -rf", 2); debugLog(strfmt("rm -rf exited with code %d",system(strfmt("rm -rf %s", path))), 3); }In addition,
However, their even though their client doesn’t allow vibe coding, it is still written in Python, which itself takes ai contributions.
Per the Makefile, this project is built using GCC. GCC itself accepts AI contributions, provided that the code is “legally insignificant” (meaning less than around 15 lines of code) or is part of test cases: https://gcc.gnu.org/ai-policy.html
For the first part: You’re probably right! I’m not sure of a safer way to do it though. This specific part is an artifact of the original method I used, which I don’t think would have worked on windows (according to some stack overflow post), but the current code might actually work fine, I just don’t have access to anything running windows and would rather not set up a VM.
Second: That’s highly disappointing! I think their policy is fairly well thought out, in a way that allows for accountability and auditability, so I might be okay with continuing to use it, I’ll have to think about it. If you know of an alternative I could use, I will happily take suggestions!
To add to the last comment, I’d also suggest not mixing logging and business code. That is to say that you should put the
systemcall on its own line, so that it is clear that it’s not just a logging call:if (!strcmp(platform, "windows") && !isSpecificPlatform) { debugLog("Falling back to rm -rf", 2); int result = system(strfmt("rm -rf %s", path)); debugLog(strfmt("rm -rf exited with code %d", result), 3); }It may just be a me problem, but I have a tendency to skim over the logging lines unless I’m intentionally reading code carefully, in which case the system call may get overlooked
I’m not sure why you did this when Tealdeer exists and has for years? https://github.com/tealdeer-rs/tealdeer
My reasoning is simple: I had never heard of it.
But also, this is an incredibly simple program and a really good way to help me learn C. Additionally, it seems like tealdeer accepts ai generated submissions, though generally discourages it. I aim to make my project as free of ai as I possibly can.
You might want to have a glance at the OpenSSF compiler hardening guide, and maybe try out ASAN (
-fsanitize=address).E.g. I get
[nobody@bb14e99a9c8e cldr]$ ./build/cldr --update --language C. caution: filename not matched: ethical-tldr/pages.C./*/*.md ================================================================= ==454==ERROR: LeakSanitizer: detected memory leaks Direct leak of 4 byte(s) in 1 object(s) allocated from: #0 0x7fa48a32c0c1 in malloc (/usr/lib/libasan.so.8+0x12c0c1) (BuildId: b8a4241051a1621937fdc46e867ba7ecb56d96ea) #1 0x7fa489e8be0f (/usr/lib/libc.so.6+0x8be0f) (BuildId: 503200d7fda94a5dc6058d7e0694e5d1dcb2e372) #2 0x7fa48a2f2761 in vasprintf (/usr/lib/libasan.so.8+0xf2761) (BuildId: b8a4241051a1621937fdc46e867ba7ecb56d96ea) #3 0x561d84213d8c in strfmt (/home/nobody/cldr/build/cldr+0x6d8c) (BuildId: 2a0f13efc2c9b12a67e7dd810a2cbdfd1866e53d) SUMMARY: AddressSanitizer: 4 byte(s) leaked in 1 allocation(s).Alrighty! I tried out -fsanitize=address and I have now patched every memory leak. There were many…






