Zig has other selling points, that are arguably more suitable for system programming. Rust's obsession with safety (which is still not absolute even in rust) is not the only thing to consider.

Zig is indeed designed specifically for such tasks as system programming and interoperability with C code. However it is not yet ready for production usage as necessary infrastructure is not yet done and each new version introduces breaking changes. Developers recomend waiting version 1.0 before using it in any serious project.

Does it require to be enabled at compilation, or it can be toggled at any time?

Works fine for me.

Telegram published a statement on X/Twitter that they are not changing any policy. The just removed misleading line in their FAQ, that stated that you can't report private chats (which you always could).

I doubt it. It is basically equivalent to buying a proprietary software license for 1% of a revenue. I doubt any large business would be willing to spend that much on a single piece of software. And it would always be only one piece of software at a time.

He already has the overhead of maintaining to C libraries, which is a lot bigger problem.

I wouldn't recomend testing any software for glibc system on a musl system.

"dinit"

It boots faster than openRC (which is painfully slow). But runit is a lot faster than systemd, and there are init systems even faster than runit. And they all already work with musl. There is even dinit system specifically designed for containers.

Systemd bloats the container a lot more than glibc.

While I do appreciate the effort, I cannot understand, who in their right mind would use musl and systemd together. For what purpose? If a person was already willing to manage a musl system, why wouldn't he also prefer sysVinit or runit or whatever?