doas
samurai
| doas | samurai | |
|---|---|---|
| 2 | 10 | |
| 51 | 797 | |
| - | - | |
| 0.0 | 3.2 | |
| almost 2 years ago | 9 days ago | |
| C | C | |
| - | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
doas
-
A simple guide for configuring sudo and doas
persist : don't prompt the user to type the password again after some time (potentially unsafe)
-
xorg sucks, use swc
Other: doas (opendoas package on void) in place of sudo, 9front or plan9 and factotum in place of Linux and PAM.
samurai
- Samurai: Ninja-compatible build tool written in C
- Oasis – a small, statically-linked Linux system
-
Ninja is enough build system
Samurai is a faster, drop-in replacement for ninja.
https://github.com/michaelforney/samurai
- samurai: Ninja-compatible build tool written in C
-
Using Landlock to Sandbox GNU Make
"If you want to do what "scrappy Google" did these days, then you should use Python + Ninja."
Or, better yet, use a simpler, faster and more portable^1 Ninja written in C.
https://github.com/michaelforney/samurai
1. The "simpler, faster, and more portable", are the author's claims, not mine. I am not the author.
- samurai: a ninja-compatible build tool written in C.
-
Moving SciPy to the Meson Build System
Why is Python not portable, as in, on which systems is "build Python and then use that to run Meson" not a reasonable option?
The CI for boson seems like it runs on platforms where Python definitely is available, but also I notice the CI uses samurai, a reimplementation of ninja with a similar motivation: https://github.com/michaelforney/samurai
Ninja is in C++ so I am even more confused at Sanurai.
Is this just an implementation-diversity thing? (which is great!)
-
xorg sucks, use swc
This means ninja is popular both on embedded for its tiny footprint (samurai is about 3k sloc and portable), and for humongous projects like Chrome, because it is infinitely scalable in complexity due to its genaration method.
-
Debian Running on Rust Coreutils
You could probably post-process samurai (a rewrite of ninja into C) into a single-file: https://github.com/michaelforney/samurai
What are some alternatives?
Vim - The official Vim repository
stm32-cube-cmake-vscode - STM32, VSCode and CMake detailed tutorial
velox - velox window manager
vivarium - A dynamic tiling Wayland compositor using wlroots
swc - a library for making a simple Wayland compositor
Microsoft Research Detours Package - Detours is a software package for monitoring and instrumenting API calls on Windows. It is distributed in source code form.
lel - farbfeld x11 image viewer
build2 - build2 build system
waymonad - A wayland compositor based on ideas from and inspired by xmonad
dwm - LEV Linux's window manager (a fork of dwm)
Rust-for-Linux - Adding support for the Rust language to the Linux kernel.