OK... and? This doesn't matter for a desktop, because: 1. Having access to the user's home directory is way more serious than being able to install drivers or whatever 2. There are a million other ways to escalate to root by obtaining the user's password I also don't understand the point of these distros, just install Arch with KDE via archinstall, it literally takes 15 minutes. Why is it that people feel the need to…
Omarchy: Any User Process Can Escalate to Root
391–400 of 590 posts
Re: Omarchy: Any User Process Can Escalate to Root
#392Other day i was hearing DHH talk on Lex's podcast on Omarchy and how he does not look at the code anymore. The guy built solid reputation with his prev contributions but now falling to AI slop.
Re: Omarchy: Any User Process Can Escalate to Root
#393Re: Omarchy: Any User Process Can Escalate to Root
#394I can fire up a Linux terminal with WezTerm and WSL2 at any point. It's customized and beautiful and totally fine. I have Codex running in one right now. I can listen to Dolby Atmos music through Apple Music or fire up a game with zero compatibility issues and full RTX support. It's just versatile like nothing else. I pair it with a gigantic 48" LG OLED TV as my monitor.
The only thing that might tempt me away from this is a fully loaded Mac Studio with 512GB of unified memory. That would be a real capability gap from my current machine. But I've contemplated wiping Windows and installing Omarchy, and I just can't figure out really what I'd gain, but what I'd lose is quite clear.
Re: Omarchy: Any User Process Can Escalate to Root
#395Omarchy has me questioning liking Rails because it just… straight up sucks? It comes preloaded with friggen ZOOM. I don’t think Windows bloat is that bad. If it makes people happy it makes people happy I guess. These guys trying it would be even more amazed at Fedora Workstation (“you can press windows and it shows all your open windows? That’s so much better”)
I don't find it to be too bloated, and the things I don't like I simply uninstall. So far its the best Linux Desktop experience I've had, and I hardly have to configure anything out of the box, most of it just works.
Re: Omarchy: Any User Process Can Escalate to Root
#396For haters: ignore them and recommend your favourite. For lovers: lobby the developers to raise their standards.
Re: Omarchy: Any User Process Can Escalate to Root
#397Re: Omarchy: Any User Process Can Escalate to Root
#398Earlier quoted context omitted.
I don't find it to be too bloated, and the things I don't like I simply uninstall. So far its the best Linux Desktop experience I've had, and I hardly have to configure anything out of the box, most of it just works.
That’s awesome! Everyone has different tastes. Personally I love GNOME because it’s extremely productive and works out of the box.
Learning the hotkeys in Omarchy is a bit of a process, but there is a hotkey to show the hotkeys lol (super + K) - and once you get used to them, its super productive, at least to me.
Re: Omarchy: Any User Process Can Escalate to Root
#399Earlier quoted context omitted.
> either have a discoverable GUI for noobs, or a configurable, keyboard driven system Absolutely wrong. Windows is both and it can be 100% keyboard driven.
Try editing key-values in Regedit using only the keyboard.
cursor up/down, page up/down, or F3 to search, hitting enter to follow directories, until you reach the key.
Hit enter on the key. The values will be displayed.
Hit tab until you are on the key you want to edit.
Hit enter. A popup with the value will appear.
Type the new value, hit enter.
A much more painless process than I anticipated, honestly, and it refreshingly uses the same conventions that used to be used everywhere in windows.
Re: Omarchy: Any User Process Can Escalate to Root
#400Earlier quoted context omitted.
There can be exploits in any security system but the architecture is sound. There's no equivalent of TCC on Linux (I mean one that really sticks), and no easy way to create one. The sandboxing isn't bad. It's obviously weaker if you do everything in the Terminal and stay in old-school UNIX territory because it wasn't designed to sandbox developer workloads. But it's a lot better than nothing, which is what Linux offe…
> The OS does actually protect you when it asks if the terminal should be able to access ~/Documents. You can say no, and then random stuff you curl|bash can't read files in that folder unless there's an exploit. How is that different from creating a new user to run that script? This has been the standard practice on Linux for decades, and it is how I run tools like Codex and Claude on my machine. I wouldn't allow AI…
I don't actually believe that macOS protects me here, as I granted this permission to the terminal five years ago...