I recently migrated to it [1], no issues so far. It doesn’t have the many features Lazy.nvim has (e.g. lazy loading of plugins that can be triggered in various ways), but this is a tradeoff I am fine with.

[1] https://github.com/bpierre/dotfiles/blob/main/nvim/lua/packa...

Somewhat relevant: I’ve been following the developer of Car Park Capital on twitter [1], a “retro tycoon game” in their own words. Yesterday, the current MicroProse [2] announced they would publish it.

[1] https://x.com/hilkojj/status/1950872926385037339

[2] https://en.wikipedia.org/wiki/MicroProse#Brand_revival_(2018...

There's also the city builder Metropolis 1998 [1]. Similar RollerCoaster Tycoon aesthetic

[1] https://store.steampowered.com/app/2287430/Metropolis_1998/

[2] (I'm the dev)

How does sudo-rs compare to run0? https://news.ycombinator.com/item?id=40205714

This one is easy: run0 is not implemented in a memory-safe language, but in C. It is likely to be hit by exploitable memory-handling bugs, like the rest of systemd, as has happened multiple times before.

An already existing and tested C software gonna have less bugs than a new rust rewrite

Sudo has had bugs filed and fixed that were found by sudo-rs.

It’s not that simple.

I don't believe that actually, neither does Ubuntu.

And if we're talking about memory bugs (which we were up to now), then definitely no.

But run0 is new C code anyway so I don't see how your claim is relevant.

A trivial Google search answers that. run0 requires systemd-type OS.

Given that Ubuntu uses systemd like the vast majority of Linux systems nowadays, how does sudo-rs differ from run0?

You might not have a systemd instance inside a container, but you still might want to switch user IDs there.

Podman has systemd inside, you can run0 in it

Surely that depends on the container? Podman doesn't artificially inject a systemd process as PID 1 by default.

Not all containers are on podman

The Lennart post about it explain it https://mastodon.social/@pid_eins/112353324518585654

He was comparing to "normal" sudo, but sudo-rs have the same problems he highlighted anyway

sudo-rs uses setuid.

run0 does not (and instead relies on systemd).

---

To answer your next question: setuid, while historic, is a bit weird, and is disabled in some environments, e.g. NoNewPrivileges.

sudo-rs doesn’t gratuitously require a root privilege daemon that regularly ships filesystem destruction and remote unauthenticated arbitrary code execution bugs.

If your bar is “I’ll tolerate such crap”, you may as well run your desktop session as root.

If sudo does this, as you imply, why do Linux system still exist that are not part of a botnet?

Implication is that systemd does this, not sudo.

Nice technical argument, did Lennart bite you while you where sleeping?

No one is rewriting systemd in rust?

I'm not aware of any serious project to do so, there's been some small projects, nothing on the scale of uutils or sudo-rs.

Chapter 2: https://www.nintendo.com/en-gb/News/2025/April/Ask-the-Devel...

Chapter 3: https://www.nintendo.com/en-gb/News/2025/April/Ask-the-Devel...

Chapter 4: https://www.nintendo.com/en-gb/News/2025/April/Ask-the-Devel...

Exact URL: https://bitbuilt.net/forums/index.php?threads/kawaii.6474/po...

I should probably word this better.

Numbers are represented in dnum using a pair of integer + precision decimals. For example, this is the number 1.0 with a precision of 18 decimals:

[1000000000000000000n, 18]

A number cannot have less decimals than none, so this is why this error exists.

<3

The GitHub repo with more technical docs: https://github.com/dai-shi/waku

Part 2: https://www.codeofhonor.com/blog/the-making-of-warcraft-part...

Part 3: https://www.codeofhonor.com/blog/the-making-of-warcraft-part...