[j3s]

going all-in on Linux is one thing, but going all-in on a specific window manager? with specific keybinds? idk, individual workflows are too specific to be prescribed like this imo.

[dimatura]

I had a similar thought, but at the same time, if people were mandated to use Windows or MacOS then that would also pretty much lock you into their respective window managers. I guess it feels more restrictive partly because it's more common to pick and choose WMs on linux. (And partly because, yeah, seems like the setup goes way beyond just a distro+WM).

[bccdee]

Also because it's a niche WM catering to pretty specific preferences. I used tiled window managers for a while but eventually I decided I preferred the no-customization, one-size-fits-all Gnome/KDE experience. A hyperland config is going to fit like a tailor-made glove—but in this case, it's a glove tailor-made for your CEO, not you.

I spun up Omarchy in a VM just to see what the fuss was about, and when I opened Neovim it booted into a plugin manager and started installing at least two dozen random plugins, including an extremely over-eager autocomplete config that filled my screen with snippet suggestions. I was instantly irritated.

[adverbly]

Actually Omarchy is also run by 37 signals so this post is effectively that them saying that they're going all in on the same stack as a group. They can obviously just change what that stack is whenever they want though. This is coming from the inventor of rails so it's not that surprising to see a push for conventions.

[mkozlows]

I bet people install it and then are like "okay, but I tweaked it up to use GNOME/Plasma/whatever"

[j3s]

i suspect this is exactly what will happen. most people don't want hyprland lol.

[hactually]

it's just an example of providing a hyper tuned tool for a given usecase. In this case, for hacking on the 37signals codebase.

[do_not_redeem]

What's so special about the 37signals codebase that you'd have trouble being productive on it running Gnome or KDE?