kiss VS oasis

For something that's more of a prepackaged build-your-own-Linux kit, KISS Linux[0] is also interesting. It's kind of a microdistro with minimal abstraction over the raw guts, and "packages" are just pre-downloaded source code repos that you compile yourself.

The "package manager" is just a shell script. The installation process[1] is entirely manual, so you control every step as you bootstrap up to building your own kernel and installing each subsystem all the way up to compiling and running Firefox. It's pretty neat.

[0] https://kisslinux.org/

[1] https://kisslinux.org/install

kiss with kiss-xorg, nsxiv, st, dmenu with script, tewi, fet.sh

kisslinux.org

A good Bash code to read is some projects from GH user dylanaraps a creator of neofetch and KISS Linux (kiss is a package manager written in POSIX sh) another repo to explore is bashbox (forked from dylanaraps/bareutils) A coreutils written in pure bash.

See KISS for examples - this is a real desktop system used by some people (including me... hopefully)

You reminded me for trying Oasis: https://github.com/oasislinux/oasis

IMO, would eliminate issues with glibc and other libraries breaking ABI compatibility. Statically-linked distros like oasis could be used as inspiration.

Oasis and its native desktop Velox.

I wonder why suckless team chose to build its browser on webkit2gtk instead of NetSurf, things like these and others like their adherence to Xorg makes me think seriously to move to Framebuffer (fbpad, fbpdf, fbff ..) or Oasis (Wayland + SWC + Velox).

When you say a fork of LLVM, am I correct in assuming that you specifically mean a fork of Clang? I don't see how the compiler backend would affect support for language extensions, regardless of whether it's an exception to that such as Tcc, Cproc, the MIR C jitter, lacc, 8cc, 9cc, and chibicc. Most of those are not for production, excluding Cproc and Tcc (at least according to Suckless or Oasis).