i3
yabai
Our great sponsors
i3 | yabai | |
---|---|---|
200 | 218 | |
9,053 | 21,195 | |
1.7% | - | |
7.6 | 9.1 | |
1 day ago | 17 days ago | |
C | C | |
BSD 3-clause "New" or "Revised" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
i3
-
Show HN: Chrome Reaper
While I believe Memory Saver was a great improvement, it only works if the tab is hidden or the window minimized. I recently learned the required state is not triggered if the tab is open but on another virtual desktop. At least this is the case with many of not all Linux window managers. Some of the many discussion threads on the topic:
https://github.com/i3/i3/issues/4353
-
Firefox 121 defaults to Wayland on Linux
> This is very true, and unfortunately there are very few people working on linux accessibility (including not me! I am part of the problem!).
Accessibility work itself ironically suffers from an accessibility problem. I brought up i3wm above, the issue for that is pretty illuminating: https://github.com/i3/i3/issues/3393
It's not that the devs are saying "this doesn't matter", the devs behind one of the most popular tiling window managers in the X11 ecosystem are saying, "this does matter, but we don't know how to fix it. We don't know what changes we'd need to make to get Orca working."
It's a really fundamental breakdown that's kind of a tragedy because I honestly believe that if accessibility communities were more heavily baked into testing and development in Linux and if this wasn't treated like two separate worlds, it would be better for everyone -- fixing accessibility concerns very often improves interfaces across the board and makes them more powerful.
But... how do you bridge that gap? I don't really know, I tried looking into Orca to see what would need to happen here and bounced off of it pretty hard, it's not a very approachable tech stack and there aren't tutorials or getting started guides. And on the other side of the issue I can preach about needing accessibility input during interface design, but I'm not in a position to give specific advice because I don't use screenreaders or alternate control schemes and I don't know what the biggest problems are.
The people who need to be involved in that process can't get involved because there's a tech barrier in place even for technically inclined people, and because the underlying software locks them out from the start. i3wm isn't ever going to get someone who's intimately familiar with Orca to jump into the conversation because the people who need to use Orca can't use i3wm. So that leaves the people who can address that tech barrier, but they don't know what to do or how to approach the problem because of the lack of involvement and because the communities are isolated from each other. So it's a chicken-and-egg problem and I don't know how to solve it.
-
"We understand" ;)
This is partially why i use tools like i3 (/ sway). i like the tool; it works extremely well for me; the design has stayed the same for 20 years; there's no profit motive to come along and fuck everything up. it just works. it is boring in the best way possible.
-
what machines have you used for development, and what do you prefer?
I use MacBook Pro (Retina, 15-inch, Mid-2014) with Manjaro as OS using i3 as a window manager. It isn't perfect, but I'm thrilled with it. I have been a Mac OS user for the last 15 years and wouldn't change what I have now for a Mac OS because I don't need more than what I'm using for development.
-
The future of /r/i3wm
Even though, we have moved the official i3 support channel to GitHub discussions, i3's biggest community is still on reddit and if things continue like that there is going to be a lot of helpful content on an increasingly closed platform.
- while in i3wm, krita dockers move downwards a bit each time they're spawned - how do I fix this?
- i3wm-like window switching for Windows
-
egui_overlay - A transparent Overlay window where you can only click the "egui parts"
for example, take i3. https://github.com/i3/i3/issues/4478
- How to start on a Linux desktop environment?
-
Machine for pentesting and general use?
For daily usage I really like kubuntu with i3wm, but it takes some configuration and getting used to the shortcuts, but it's well worth it
yabai
-
My MacBook setup (the 2024 version)
It exists! Check out [yabai](https://github.com/koekeishiya/yabai), which is nicely paired with [skhd](https://github.com/koekeishiya/skhd).
-
Ask HN: Best Hacks for a Ultrawide Monitor?
I have a 49 inch CRG9 and the best recommendation for window management is Yabai (https://github.com/koekeishiya/yabai) along with skhd (https://github.com/koekeishiya/skhd). Yabai is a greedy window management solution that tries to fit opened applications in given space and skhd let's you easily jump between those using keyboard shortcuts. This has massively improved my ultrawide experience.
Only disclaimer is, configuring yabai has a slight learning curve.
-
Is there an app that does this Windows feature?
Want something free that's better than tiling on Windows? Yabai.
-
Yabai – A tiling window manager for macOS
Here it is. There is no visualization of the stack, which apparently Stackline in the other comment supports, but I don't tend to need that. Just being able to move between the windows is good enough for me.
https://github.com/koekeishiya/yabai/issues/203#issuecomment...
-
Asahi Linux folks are doing us a solid with WPA3 fixes
I use Yabai on my Macs without SIP enabled. Here’s a list of the features that absolutely require SIP to be disabled: https://github.com/koekeishiya/yabai/issues/1863
But you don’t need to disable SIP just for tiling.
> there's still a ton of tinkering and tweaking you need to do to get Yabai really working correctly
This is pretty much true of basically every tiling window manager on Linux, too.
For me, using Nix-Darwin for MacOS and NixOS has drastically simplified my tiling window manager setup after initially doing the work to figure out my ideal config.
-
macOS Containers v0.0.1
SIP is a feature that protects you from malicious actors with root (admin) access on your device. After they've encrypted your photos and drives and changed your passwords, it prevents them from making your machine unbootable by deleting or altering system binaries. As a side effect of this protection, you give up certain freedoms to customize your system.
https://github.com/koekeishiya/yabai
For instance requires SIP to be disabled.
- Yabai: A binary space partitioning tiling window manager for macOS
-
Ask HN: Why does Apple refuse to add window snapping to macOS?
This is disproven by the fact that Yabai [1] can instantly swap spaces with SIP disabled.
[1] https://github.com/koekeishiya/yabai
-
[Serious] I don't get why people like Mac and I feel like I'm missing out
If you find the native window management lackluster (like I do), you can install a window manager like Amethyst, or yabai, veeer, or many others.
What are some alternatives?
sway - i3-compatible Wayland compositor
Amethyst - Automatic tiling window manager for macOS à la xmonad.
awesome - awesome window manager
Rectangle - Move and resize windows on macOS with keyboard shortcuts and snap areas
bspwm - A tiling window manager based on binary space partitioning
vscode-vibrancy - Enable Acrylic/Glass effect for your VS Code.
wslg - Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
Karabiner-Elements - Karabiner-Elements is a powerful utility for keyboard customization on macOS Sierra (10.12) or later.
xmonad - The core of xmonad, a small but functional ICCCM-compliant tiling window manager
alt-tab-macos - Windows alt-tab on macOS
tmux - tmux source code
MonitorControl - 🖥 Control your display's brightness & volume on your Mac as if it was a native Apple Display. Use Apple Keyboard keys or custom shortcuts. Shows the native macOS OSDs.