To be clear I'm accusing the distro to steer people in a certain direction, I'm arguing that it's something that people who already have a certain set of political beliefs will be drawn to.
>That you think it's all about UNIX guru LARP I have to question how many Omarchy users you actually engaged with because I've mostly met humble and friendly folks. YMMV.
I mostly base myself on the tweet wall posted on Omarchy's website, because it features (or featured, back when I looked at it) a bunch of former Mac users patting themselves on the back for being such 1337 h4x0rs for... mainly using a tiling WM, as far as I can tell.
As someone who has been using Linux and tiling WMs for over two decades it's a bit baffling to look at frankly. I guess I'm a bit salty that I missed out on millions of dollars by sharing my config files.
>I've been working a lot on customization and upstreamed some patches and I have no idea what would count as poorly configured.
I obviously haven't surveyed the entire ecosystem but the base scripts shipped with the distro (which I presume are mostly DHH's work) look more like a personal dotfile compendium than something a serious distro would ship. I'm talking about stuff like this: https://github.com/omacom/omarchy/blob/1e859d37cb7fef6ac6874...
That "format-drive" function is particularly entertaining, I think.
Regarding third party code, the small handful of github projects I looked at were the most spaghetti of vibecode, e.g. https://github.com/ETroll/omarchy-airplay/blob/master/bin/om...
This may not be representative of the ecosystem at large, admittedly, but given the huge focus on vibecode/agentic stuff in the marketing, I think this is not an unexpected outcome.
Beyond that, using your own, worse package manager instead of leveraging Arch's existing capabilities (but also still using Arch's packages for some things) is just terrible design.
>That you think it's all about UNIX guru LARP I have to question how many Omarchy users you actually engaged with because I've mostly met humble and friendly folks. YMMV.
I mostly base myself on the tweet wall posted on Omarchy's website, because it features (or featured, back when I looked at it) a bunch of former Mac users patting themselves on the back for being such 1337 h4x0rs for... mainly using a tiling WM, as far as I can tell.
As someone who has been using Linux and tiling WMs for over two decades it's a bit baffling to look at frankly. I guess I'm a bit salty that I missed out on millions of dollars by sharing my config files.
>I've been working a lot on customization and upstreamed some patches and I have no idea what would count as poorly configured.
I obviously haven't surveyed the entire ecosystem but the base scripts shipped with the distro (which I presume are mostly DHH's work) look more like a personal dotfile compendium than something a serious distro would ship. I'm talking about stuff like this: https://github.com/omacom/omarchy/blob/1e859d37cb7fef6ac6874...
That "format-drive" function is particularly entertaining, I think.
Regarding third party code, the small handful of github projects I looked at were the most spaghetti of vibecode, e.g. https://github.com/ETroll/omarchy-airplay/blob/master/bin/om...
This may not be representative of the ecosystem at large, admittedly, but given the huge focus on vibecode/agentic stuff in the marketing, I think this is not an unexpected outcome.
Beyond that, using your own, worse package manager instead of leveraging Arch's existing capabilities (but also still using Arch's packages for some things) is just terrible design.