Our great sponsors
sway | i3 | |
---|---|---|
613 | 200 | |
13,672 | 8,950 | |
2.3% | 1.3% | |
9.2 | 7.8 | |
3 days ago | 19 days ago | |
C | C | |
MIT License | BSD 3-clause "New" or "Revised" 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.
sway
-
"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.
-
Firefox on the Brink?
I also have crashes on sway, but there’s a rough workaround now which prevents the issue totally.
I believe there’s a design issue with Firefox and GTK handling input events; some Wayland compositors have workarounds but others do not.
https://github.com/swaywm/sway/issues/7645
https://bugzilla.mozilla.org/show_bug.cgi?id=1743144
Firefox is my preferred browser and I hope we can keep its engine alive in this era of Chrome dominance.
- Framework 13 with AMD Ryzen 7040 Series Makes for a Great Linux Laptop
-
On Desktop GUI Minimalism
Sway is fast, minimal, and flexible. Their recommended tools/addons are worth a look: https://github.com/swaywm/sway/wiki/Useful-add-ons-for-sway
From that list I use greetd + tuigreet as my login manager, sway-launcher-desktop for FZF-powered app launching, and wob for lightweight brightness and volume display (send '50' to the wob socket and it'll show 50%; it doesn't get simpler).
-
The technical merits of Wayland are mostly irrelevant
Sensitive features like screenshots, input methods, screen locking and whatnot are behind extensions (or portals). I'm not familiar with the state of GNOME/KDE/Flatpak, but at least on the wlroots side of things it is true that currently these extensions are enabled and accessible by any process that can talk to the Wayland socket (breaking those security benefits, as you say). This is changing with protocols such as security-context that allow a sandbox engine like Flatpak (or your custom scripts) to restrict what features apps can use. (so your browser can't register an input method, or some random app can't lock the screen)
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/m...
-
Rethinking Window Management in Gnome
sway does all those things very well: https://swaywm.org/
-
Using nwg-wrapper for a HUD of help for sway modes
I've added it to https://github.com/swaywm/sway/wiki/Useful-add-ons-for-sway
- What is a good windows tiling manager for beginners?
-
Wayland Is Pretty Good
https://github.com/swaywm/sway/issues/4763
sad to see another linux api design failure
- A linux newbie has installed and configured Arch. Minimalist graphical capabilities?
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:
-
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.
-
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?
-
What's the difference between Gnome and KDE? Do applications written for one work in the other?
Some window managers are meant to be used as-is, and provide a minimalist yet functional environment that use very little resources or give power users an almost HUD-like interface. Examples of those window managers are OpenBox and i3wm for X, and Weston and Hyprland for Wayland
-
I created a side file tree picker workaround for Helix Editor in i3
i3, https://i3wm.org
-
tiling window manager
I did use i3 exclusively for a few years. The reasons I chose it were
-
i3 vertical dock
I don't think you can with base i3. See this open issue on the subject: https://github.com/i3/i3/issues/1129
-
best lightweight linux distro for old laptop and gaming
well, it depends. It was better experience than FreeBSD 7.2 that's for sure. :) It was running Xorg with https://i3wm.org, a web-server, XMPP-server, PostgreSQL, few bots and dovecot / postfix (e-mail server). It was doing fine routing internet for 2PCs and a WiFi router for 10 years until its HDD died. For gaming... erm... I was able to play something like Theme Hospital or Syndicate Wars in dosbox. You have to understand any OS is just software it doesn't make magic. With minimalistic Desktop Environment like Xfce, LXDE or even barebones i3wm you can put your hardware to use with Arch Linux.
What are some alternatives?
Hyprland - Hyprland is a highly customizable dynamic tiling Wayland compositor that doesn't sacrifice on its looks.
wayfire - A modular and extensible wayland compositor
river - [mirror] A dynamic tiling Wayland compositor
awesome - awesome window manager
awesome-wayland - A curated list of Wayland code and resources.
bspwm - A tiling window manager based on binary space partitioning
qtile - :cookie: A full-featured, hackable tiling window manager written and configured in Python (X11 + Wayland)
wslg - Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
Waybar - Highly customizable Wayland bar for Sway and Wlroots based compositors. :v: :tada:
dmenu-wayland - dmenu for wayland-compositors