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?
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?
Short answer: yes, you can do exactly that.
Firefox is not done. It just became spyware, but all the forks can still benefit from FOSS license of Firefox. In the same manner as Vivaldi or Brave or Ungoogled chromium etc.
Librewolf, Waterfox, Mullvad, Floorp…
Does it have a separate add-on store?
If Mozilla gets blocked, people would just install some other browser (probably, something from Russia). I do not see how this helps anyone but the government itself. And departure of hundreds (if not thousands) of western companies did nothing to the Russian government, some problems with a browser with almost non-existent userbase would have the same effect. It should be quite clear by now that such tactic simply does not work.
Well, I know it used to be available and officially supported through available installation script. I do not have bazzite installed right now and their website does not have a proper documentation, so I can not check if it is available now.
Fortunately, it does not usually cause high load, but it still exists. The only thing I can recomend here is to always check if the dependencies of any package you install in container require to run in the background and avoid those which do.
The lag would be noticeable when you launch Firefox with stopped container (for example after reboot or manual stop).
Toolbox is effectively the same thing as distrobox. It is a linux distro inside docker-like container. They even use the same images.
Maybe, I do not use bazzite and cannot check. But it used to be a feature. You can, of cause, start distrobox at startup, but literally running almost two operation systems might not be the best for performance and RAM usage.
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.