also from my totally surface level understanding both sudo and doas “elevate your privileges” which is supposedly unnecessary attack surface. run0 does it in a better way which I do not understand.

sudo and doasare setuid binaries, a special privileged bit to tell the kernel that this binary is not run as the user starting it, but as the owner. A lot of care has to be incorporated into these to make sure you don’t escalate your privileges as the default interface is very limited, being a single bit.

Another issue with this approach is that since you’re running this from your shell, the process will by default inherit all environment variables, which can be convenient, but also annoying (since a privileged process might write into your $HOME) or upright dangerous.

run0doesn’t use that mechanism. systemd is, being a service manager at its core, something launching binaries in specialized environments, e.g. it will start an nginx process under the nginx user with a private tmp, protecting the system from writes by that service, maybe restrict it to a given address family etc. So the infrastructure to launch processes – even for users via systemd-run– is already there. run0 just goes one step further and implements an interface to request to start elevated (or rather with permissions different from their own) processes from a user’s shell.

Classic solutions do it like this:

1. user starts binary with setuid (let’s say sudo) that runs with root (because that’s the owner of the binary) privileges in their shell. Since this is a child process of their shell, it inherits all environment variables by default.
2. sudochecks /etc/sudoers if that user is authorized to perform the requested action and either denies the request, performs it or asks for authentication.
3. a new process is spawned from it, again inheriting the environment variables that were not cleaned, as you can’t get rid of variables by forking (this is often an issue if you have services that have their secrets configured via environment variables)

With run0:

1. user starts run0 binary as a user process. This process inherits the environment variables.
2. run0 forwards the user’s request via interface to the running systemd process (pid 1 I guess). That process however does not inherit any variables by default, since it was started outside the user’s shell.
3. systemd checks if the user who started the run0 binary is allowed to perform the requested operation and again, either denies the request, performs it or asks for authentication.
4. a new process is spawned from it, but it will only receive the environment variables that were explicitly requested as there’s no inheritance.

At least that’s my understanding, I haven’t looked too much into it or used it yet.

That’s why I wrote about “technology faith”, in contrast to the topic “science faith”, because while I think the dangerous idiot is wrong as always, the related issue (as technology is applied science) exists.

Regardless, her motive is just to discredit proper scientific methods and results she doesn’t like, while my point was about technology and its limitations that people don’t understand yet think will fix everything.

I always find this a little funny… Like I always hear complaints how the FDA is overbearing and stuff

It’s big corpos who’d love to continue using these additives that launch these claims via proxy into the public. Similar to how McDonald’s made sure people think the US is a country of frivolous lawsuits because they were ordered to cover a woman’s medical costs after a jury found them guilty. Purposeful misrepresentation of facts

First off, Candeath Omens can go fuck herself.

I do think however that there is a weird technology faith in that people believe technology will fix all issues long term or improve or all aspects of our lives. Like when people say AI will fix global warming / climate change… dude, it can’t even properly take orders at a McDonald’s, which is traditionally one of the least qualified jobs. And if you ask an AI how to stop it, it’ll just tell you what we already know, which people haven’t been doing for years. Because that’s what am AI does.

It’s mostly the people neither actually engineering the technology nor studying the actual issue that believe this. But it’s a huge driver in the discussion.

Which is exactly what I’d use this for, were it not for the fact that I switched to the windows version of SV anyways. It wants an old system OpenSSL lib that’s insecure and I don’t have it. So wine with Windows version it is.

Ich als solidarischer Westdeutscher habe meinen Teil getan und alle meine Immobilien in Leipzig für gemeinnützige Zwecke zur Verfügung gestellt

The base game is free, the price is for DLC.

Ah, I see. Makes sense. I have seen some horrible LaTeX code at uni where someone didn’t follow your simple rule:

let LaTeX do it’s job.

The decision LaTeX makes are often very good, and the problem is often that what one thinks is better comes with even bigger downsides.

Now, once we get into tables… Ugh

Currently working in LaTeX for work.

I don’t think you really need looseness (I assume you want to avoid single lines?), you can rather increase the badness of them so that they’re avoided through other means.

Manual line breaks I only use in tables (thanks tabularray author). In text, I don’t think I have any.

Negative vspace I also don’t have, what’s your use case? I can imagine it for very specific tasks (a special page like a title page it something similar where everything is set very precisely) but for normal writing, I didn’t encounter it.

All in all, I think LaTeX shows its age, but the huge ecosystem is the main reason it’s still a good choice despite a little of shortcomings like the arcane macro system, features that are seemingly impossible to implement like accessibility (

(but it’s still leagues ahead of word)

My current document approached 50 pages with about 10 tables, 3 figures (tikz) and 10 bibliography entries and it’s perfectly handleable. Just informing having to do that with word gives me agony. I worked on the same type of document in word that was kind of an earlier draft by someone else and stuff broke left and right, and that was without the more complex formatting that I later employed.

As someone else answered, I’m also looking forward to typst. Unfortunately, PDFs generated by it are currently much larger than through LaTeX (https://github.com/typst/typst/issues/895, fix currently not in any stable version) and package import is a preview. Some features aren’t implemented yet but would be really nice, the syntax seems really sane and it’s fast, so I’m optimistic it can become a strong contender.

I guess that’s where the advantages come into play the most. I only use it for a handful of machines (2 notebooks, one workstation, an SBC and 2 VPSs) and it’s still a great solution, though there is quite the overhead for the first setup.

Anyhow, that doesn’t mean that it’s more work in total than other distributions. The module system catches a lot of configuration errors for you which means you basically never and up with a “broken” configuration, and even if you did, you could select an older generation (more correct way to say rolling back on NixOS). Sure, the configuration might not do want you intended, but it will most likely be functional.

This even goes so far that some modules detect common configuration pitfalls for applications, like headers not being inherited because they got redefined.

Hence the comment about “bias automation”