That's not a fair comparison at all. Busybox is specifically optimized for size, and to accomplish that, leaves out a large number of GNU compatibility features; uutils is designed to mimic GNU as closely as possible, and I'm assuming that the binary you're looking at is not the "small-release" build. Just to see what that looks like, I've built it that way now and that puts it under 7 MiB; still much larger than busybox, but it shows how much the optimization choices matter.
I think you're making some poorly-researched assumptions.
In the embedded world, there often aren't "system libraries," depending on just what you're targeting. But if, for some reason, you really do want to use libc but not the Rust standard library, you can certainly do that; for instance, here's a crate that reimplements the Rust standard library's output and formatting capabilities using libc: https://github.com/mmastrac/rust-libc-print
Rust provides essentially the same memory control as C does. You can also have inline assembly in Rust, just as in C.
There are a variety of reasons why Rust binaries tend to be bigger unless you follow some of those guidelines, but the biggest one (and actually not something those guidelines recommend changing!) is that C is generally dynamically linked against a system version of the C standard library, whereas Rust binaries are statically linked by default, meaning that the binary is actually self-contained.
Oh, I thought by "already" you meant right now. I would expect that you can use any Wayland-compatible compositor once their Wayland support is complete, yeah.
Do you have a different recommendation for how to display unnameable types in error messages? I'm sure the compiler team would consider any suggestions.
This is hilarious. I'm not sure how often anyone would actually need to verbalize arbitrary binary data, but I do see an advantage over base64 since the English letter names are so often phonetically similar.
I understand having severe philosophical disagreements with the Rust project, with the majority of Rust users, or with the uutils project specifically. What I don't understand is this part:
If you go to the website of the Rust programming language nowadays, one of the first things you'll notice is that their primary communication platform is Discord. Yes, you read it right - their primary communication platform is Discord, a proprietary spyware program that is owned by a Chinese investment company and has backdoors to various other national intelligence agencies too.
Rust did have an official Discord, years ago, before switching to Zulip (alongside other official communal hubs, most prominently the Discourse forums that the author complains about next). But this was written in March and specifically says "nowadays", and I cannot find any mention of Discord on the Rust website.
If you drive a car, have you read the entire owner's manual for every car you've owned? If you're a homeowner, how about your hvac system? What about your system shell? Your compiler(s)?
At some point you need your tools to be intuitive enough that you don't need to read an entire manual in order to do your work.
Sure, Old English. But the commenter isn't writing in old or even middle English.