I’d place i3 and Sway deeper down the rabbit hole …
I mean they are, but my mind and fingers have been so twisted by vim that I can’t really interact with floating wms without feeling honestly pretty intense discomfort. I see people having fun with their cool Plasmas etc and I wish I could make the leap, but every time I try I just bristle at all the mouse use. The lack of control makes me feel like I’m trying to use a computer while wearing oven mittens.
I made the switch from i3 to kde with https://github.com/tilorenz/compact_pager and keyboard shortcuts similar to tiling WMs. Check out my config for keyboard shortcuts for window management with curl https://raw.githubusercontent.com/jowodo/config/refs/heads/main/plasma/window-managment.kksrc | grep -v '=$'. You could even import them into your kde settings and they will be added. PS.: yes I use meta AND alt, because I also use windows (where alt is my mod key) and macos (where option is my mod key) at work.
My point is - why go backward? You already have your Sway[1] based setup, configured just the way you like it, with the ability to switch various components in and out. What does a monolithic[2] environment like KDE have to offer you?
Assuming it’s Sway and not i3 because I assume you have already switched to Wayland. You switched to Wayland, right? You need to switch to Wayland. Why are you not switching to Wayland? ↩︎
, Yes, you can tweak KDE, but since all the various parts were created to fit together switching one will always result in awkward UX. ↩︎
I guess I hadn’t thought of it that way. Maybe I already have the wm experience that works for me, and I can just load up KDE when friends come over and I want to provide a more approachable UI for them.
That’s an odd statement. I’d place i3 and Sway deeper down the rabbit hole, being build-your-own[1] as opposed to packaged deals like KDE.
in the sense of building a configuration - not in the sense of compiling code. ↩︎
I mean they are, but my mind and fingers have been so twisted by vim that I can’t really interact with floating wms without feeling honestly pretty intense discomfort. I see people having fun with their cool Plasmas etc and I wish I could make the leap, but every time I try I just bristle at all the mouse use. The lack of control makes me feel like I’m trying to use a computer while wearing oven mittens.
I made the switch from i3 to kde with https://github.com/tilorenz/compact_pager and keyboard shortcuts similar to tiling WMs. Check out my config for keyboard shortcuts for window management with
curl https://raw.githubusercontent.com/jowodo/config/refs/heads/main/plasma/window-managment.kksrc | grep -v '=$'. You could even import them into your kde settings and they will be added. PS.: yes I use meta AND alt, because I also use windows (where alt is my mod key) and macos (where option is my mod key) at work.My point is - why go backward? You already have your Sway[1] based setup, configured just the way you like it, with the ability to switch various components in and out. What does a monolithic[2] environment like KDE have to offer you?
Assuming it’s Sway and not i3 because I assume you have already switched to Wayland. You switched to Wayland, right? You need to switch to Wayland. Why are you not switching to Wayland? ↩︎
, Yes, you can tweak KDE, but since all the various parts were created to fit together switching one will always result in awkward UX. ↩︎
I guess I hadn’t thought of it that way. Maybe I already have the wm experience that works for me, and I can just load up KDE when friends come over and I want to provide a more approachable UI for them.