maybe i should build something like omarchy that isn't, you know, omarchy
Replying to @ariadne@social.treehouse.systems
@ariadne i've been considering the same for a long time. I went so far as to set out goals for myself, but I've quickly realized that I dont (nor do most people) have capacity for such an endeavor *on their own*.
Definitely the hard part of organizing such a thing is the key consideration.
If you want help coordinating that, hmu :)
I've got thoughts. (Mostly I think that nix/guix, a functional approach to software & package management is the correct path forward for maintainability and customization purposes)
Replying to @scien@social.linux.pizza
@scien your thoughts are basically the opposite direction of what a productized form of linux should look like.
for example, there should not be 'package management'. (there should, but it should not be a focus *at all*)
we are designing for people who want to use their computer, not customize their computers.
Replying to @ariadne@social.treehouse.systems
@ariadne it's mostly about the labor of the team, is the reason I'm pushing it forward. There's nothing antithetical about functional packagement management to consumer usage.
See experiments such as "snowflakeOS" that place its design behind a gui interface: https://snowflakeos.org/
Also see: my subsequent comment about drivers
snowflakeos.org/Replying to @scien@social.linux.pizza
@ariadne (An additional advantage is the functional management of hardware drivers, which allows a significant amount of issues that a smaller team has to deal with be much more manageable. See nixos-facter, nixos-hardware modules, and my own extension, nixos-facter-compat: https://codeberg.org/boneraven/nixos-facter-compat )
codeberg.org/boneraven/nixos-facter-compat