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.

This is an instance of that recurring trope of coding something better out of pure spite

I could only wish to be this cool.

So, I decided to learn C from scratch
...
on my own in just the past 3 days

Really impressive, great job! What resources did you use for learning?

So... C code is faster than python. We knew that. Thanks for the better performing rewrite. Now do it in rust 🤓

Consider using a different name for the project if you care for searchability. There's already Unicode CLDR Project.

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).

https://github.com/tealdeer-rs/tealdeer Rust TLDR

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

I'm not sure why you did this when Tealdeer exists and has for years? https://github.com/tealdeer-rs/tealdeer

I wish people still had shame.

Python isn't for command line utilities that you intend to distribute to others. It's for personal one-off scripts.

I mean, FFS, if you're gonna vibecode something, why not pick a fast language? The fact that they can't even tell the LLM to use the right technology shows that they are a complete imbecile

Dependancies

[Optional] wget can be installed for less reliance on other projects using ai, if wget is not found, curl will be used instead

1. Small typo: dependencies.
2. Is curl using AI in its code now?

Thanks for your work!

excellent. however if you are making a point about AI not being as good s a quality developer, you are missing the point.

CEOs don't give a shit about quality and effectiveness. it is all about getting rid of labor costs. once all he few remaining providers of service are absorbed, we take what they give and pay through the nose. monthly.

Oh yeah this is bound to be maintained

Hell yeah!

C ftw, but seriously, calling an entire language(python) AI slop is going too far, though I will admit python has been responsible for slop code even before LLMs. My opinion on the matter is, efficient use of LLMs will usher a push to go back to hardware level languages like C, as all the benefits of python(except the awesome collection of libraries it has unfortunately accumulated) are kind of moot when you have a machine capable of outputting any boilerplate you ask of it; beyond that I do not trust LLMs to write logic unless its a well known and named algorithm like reversing an array or a linked list.