omarchy

Omarchy tries resolving this https://github.com/basecamp/omarchy

My 32GB RAM M1 is a fantastic machine, but it's getting old for the type of work I do. And I can't upgrade the RAM. I installed Omarchy via Asahi Alarm [1] and have been running it for 3 weeks without issues. I spent half a day setting everything to my taste (keyboard bindings, monitors, waybar, etc.), and I'm still getting used to Hyprland, but I have a fast machine. RAM usage with everything I need open is considerably lower than on macOS (80% -> 50%), and I don't have to pay a monthly subscription for every little piece of software not built into macOS. Asahi isn't perfect (touchpad rejection being my main issue), but I can live with the inconveniences. This is still a very good machine, and I can't afford a new one right now. [1] https://github.com/basecamp/omarchy/pull/1897

What about just ignoring package signatures? https://github.com/basecamp/omarchy/blob/master/default/pacm...

Technically they are using (abusing?) a container containing Windows 11. https://github.com/basecamp/omarchy/blob/master/bin/omarchy-... The container they spin up: https://github.com/dockur/windows And vanilla Arch is still in play, the only thing they do is a shit ton of configuration so you don't have to do it yourself. Basically dotfiles but on steroids. It's also great for some inspiration if you want to do some ricing yourself.

Looking through the commit graph for Omarchy is wild. It has 2000+ commits, most of which contain the type of intermediary work pushed into the trunk that you'd see from a jr who doesn't squash their local work Also some gems like: https://github.com/basecamp/omarchy/commit/af72a45dbd4358bca... > Remove non-existent vibe-code hallucinated options and clean up theme files or https://github.com/basecamp/omarchy/commit/4fedfbe9f19303046... There's also Omakub[0] which was sort of a precursor to Omarchy that gives users the `wget <some url> | bash` as a means of installation where the install script is a thin wrapper around another `eval $(wget <some url>` that then git clones a repository and executes a 3rd script. That's definitely the kinds of patterns I'd expect some prolific software engineer to use and also encourage complete novices to