drakerossman
Making a Chess Engine in Zig
A Comparison of Arenas in Rust
Ringboard: Clipboard Manager for Linux Written in Rust
Run Diablo in the Browser
Rust Async Closures MVP: Call for Testing
Hybrid Teams Are the Worst
Hybrid Teams Are the Worst
Hybrid Teams Are the Worst
High-precision date/time in SQLite
The Hitchhiker's Guide to Building a Distributed Filesystem in Rust
Panic at the Async Runtime Shutdown
The Missing Parts in Cargo
Rust for Filesystems
From the Lab to the Trading Floor: Designing for Expert Users
Nix on macOS – The Good, the Bad and the Ugly
Graphical effects in Duke Nukem 1 and 2, part 1
Abstract Heresies: Monkeys vs. Shakespeare
Surprises with Rust's `as` (and Python Division)
LLM vendors are incredibly bad at responding to security issues
Nix on macOS – The Good, the Bad and the Ugly
Further Simplifying Self-Referential Types for Rust
Using unsafe in our Rust interpreters: easy, debatably ethical performance
Ergonomic Self-Referential Types for Rust
Also check the "nix" tag at blog.
Sway is just i3 for Wayland, which in turn means you have multiple workspaces (which are also potentially mapped to multiple monitors). You assign workspace a label (number, or text, or emoji), and you may also bind some application to always open on that workspace. Or you just get a habit of putting specific applications to only specific workspaces. Your entire navigation then sits in your muscle memory - finger on the mod key (win or alt or ctrl - whatever), another finger on the digits row for the workspace index - and you're there.
It's a tiling WM, so you don't spend time arranging windows - they already take the full desktop real estate evenly split between them, and you can also adjust size of each window separately. Again, this sits in your muscle memory.
Point is - no mouse is needed to navigate through workspaces and windows.
You may read my blog post about setting sway up (on NixOS) here:
https://drakerossman.com/blog/wayland-on-nixos-confusion-con...