N1
i3
Our great sponsors
N1 | i3 | |
---|---|---|
1 | 200 | |
24,788 | 8,950 | |
0.1% | 1.3% | |
0.0 | 7.8 | |
over 1 year ago | 19 days ago | |
JavaScript | 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.
N1
-
Fed up with the Mac, I spent six months with a Linux laptop
> - Finding a mail client I don't hate on linux is tricky. I've never been able to get on with the console clients, and I actually quite like Mac Mail. Thunderbird is kinda okay.
If you're not a mailing list based developer, I would recommend Nylas Mail, which is both snappy any polished.
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?
sway - i3-compatible Wayland compositor
awesome - awesome window manager
bspwm - A tiling window manager based on binary space partitioning
wslg - Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
xmonad - The core of xmonad, a small but functional ICCCM-compliant tiling window manager
tmux - tmux source code
exwm - Emacs X Window Manager
dwm - LEV Linux's window manager (a fork of dwm)
kwin-tiling - Tiling script for kwin
j4-dmenu-desktop - A fast desktop menu
polybar - A fast and easy-to-use status bar
Rectangle - Move and resize windows on macOS with keyboard shortcuts and snap areas