The most battletested way is via bindings to other languages. Ex. mlua with luau sandboxing Or Javascript via v8 or deno_core

There are also a few languages implemented in rust like rhai

There is also the option of compiling the user code to wasm and using wasmtime to run it

1. Due to the failings of the electoral college system, my state was almost guarenteed to vote the same way as it has for the last 30 years
2. I did not strongly agree with either party/candidate
3. I dispise the current two party system that both major parties are incentivized to maintain
4. Voting for a third party who is incentivised to push for change via ranked voting and other methods does aid them even if they don’t win

If my state was likely to be contested, I may have voted differently. Voting for a third party in my case however had a greater impact than fighting or joining the tide of my state

I’d look into the git-maintenance’s prefetch task. From what I understand, that is more or less what you are looking for. Then just run any old http(s) server and clone them from that https://git-scm.com/docs/git-maintenance

There is also writefreely. It is fairly basic, but says it supports “publish[ing] to multiple blogs from one account”. Haven’t really used it, but it looks kinda cool imo

https://github.com/writefreely/writefreely

Standard forgejo shoutout. It is a fork of gitea with more features following the foss philosophy. It is codeberg’s backend https://forgejo.org/2024-02-monthly-update/

Primary code editor: helix

Graphical debugger and certain IDE features: vscodium

Lots of open source language servers: clangd, rust-analyzer, perl-navigator, …

Makefile to compile-comands.json: bear

TUI file manager: yazi

Better Grep:ripgrep

Debugger: gdb(gnu debugger)

I’m sorry but I don’t understand whatever argument you’re making. I did the line count on my phone via termux because I was in a rush, so i’m aware the counts may be inaccurate. I should have made that clear in my earlier reply.

I do, however, hold to the fact that any sudo implementation will be more complicated than doas. Sudo, as a project, has more options and usecases than doas so it also has more posibilities for bugs or misconfiguration for the user.

I’m unable to tell what codebase your are refering to with you’re grep arguments, sorry.

1. Opendoas has a significantly smaller codebase. It only has 4397 lines of code compared to Sudo-rs’s staggering 35990 lines.

2. It has a very simple config file which can do everything I want in less than 6 words.

3. It is a soft fork of BSD’s doas package and receives frequent audits(something I find reassuring since it is a method to gain root access on my system.

4. I don’t want or need 99% of the features sudo provides so I appreciate the simplicity and lightness of opendoas

Cool, but I’ll stick with opendoas