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.

And yet, you haven't said it either

What is the reason?

Something similar to the tiling model also dominates on small screens, like phones.

And while I've used tiling WMs on Linux for well over a decade (probably nearing two), it does seem that plenty of people will prefer the familiar over trying something new, c.f. Win8's reception (I've never used it myself)

Glad you are enjoying C. As one of my proffesor's espoused, "It is God's language". As a C++ developer, I cannot recommend {fmt} enough.

Why in rust? I mean it would be less faster, right? If speed is of the essence ofc.

We use CLDR quite a bit — and coincidentally, we often jokingly call it TLDR.

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

Is there another thing to use? At least for the flow(s) of "encrypt, transfer, decrypt" or "sign, transfer, verify" for binary files. BSD licensed, preferably.

EDIT: minisign was mentioned on the talk... not in the most positive way but would still trust (after they get their shit together of course); however would never trust "age" with what they did

Already exists and isn't vibecoded https://github.com/tealdeer-rs/tealdeer

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.

Changing what people are used to would result in even fewer people being willing to switch over from Windows and macOS.

Ohh, not bad! If I feel like I need to change it, tlcr is probably the best option

Just go with tlcr!

yes! However, I found it very frustrating to use and it kept leading to ludicrous errors beyond my wildest dreams. So I made my own function that works better and easier.

Update to this, ~~I actually just fixed that bug, and ~~I went through the first section of the hardening guide. Changes are now pushed to main and I released v1.2.1

Do you know about the sprintf function?

damn! I guess I should have looked it up before going with the name. I just liked the play on tldr, cldr.

Mostly just w3. Occasionally I had to look up some stuff for more “niche” use cases, but for the most part I just learned from w3.

I already have experience with programming in general, so the hardest part was learning the syntax, and strings… oh god strings are so bad in C, I had to make a new function called strfmt that works like printf but just for returning a formatted string.

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

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?

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.

Ah damn! That's one of the things I had told myself I needed to make sure I checked, but I forgot! Thanks! I'll look into this tomorrow. Like I said, I literally learned C over the last 3 days to make this, so I'm always happy to learn more!

There's also https://github.com/tealdeer-rs/tealdeer

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