Wayfire 0.8
wayfire.org
Wayfire 0.8
1–10 of 73 posts
Re: Wayfire 0.8
#2I gave Wayfire a shot a bit earlier in the year, but as I am a Dvorak typist and https://github.com/WayfireWM/wayfire/issues/1601> is marked as "wontfix", I decided to stick to Awesome for the time being. It did run like a dream, though, even on my ancient potato, so if the keybinding issue does get fixed at some point I may well switch over.
Re: Wayfire 0.8
#3Anyone using it daily? I'd love to hear about what makes the cool animations.. well, cool. My desktop is pretty boring right now.
Re: Wayfire 0.8
#4I gave Wayfire a shot a bit earlier in the year, but as I am a Dvorak typist and https://github.com/WayfireWM/wayfire/issues/1601 > is marked as "wontfix", I decided to stick to Awesome for the time being. It did run like a dream, though, even on my ancient potato, so if the keybinding issue does get fixed at some point I may well switch over.
Oof. That is not an acceptable way to treat the issue. It’s one thing to say you don’t the time & cycles, but it’s another to WONTFIX it twice with a clear usability problem.
Re: Wayfire 0.8
#5Anyone using it daily? I'd love to hear about what makes the cool animations.. well, cool. My desktop is pretty boring right now.
I rather have a boring and stable desktop than these trend of the week WM:s. Time will tell if they even stick around, and become a reasonable daily driver.
In wayland-land the only one I managed to use for a couple of days without crashing was sway in 2022. Both their last release and sway-git is crashy
Re: Wayfire 0.8
#6I gave Wayfire a shot a bit earlier in the year, but as I am a Dvorak typist and https://github.com/WayfireWM/wayfire/issues/1601 > is marked as "wontfix", I decided to stick to Awesome for the time being. It did run like a dream, though, even on my ancient potato, so if the keybinding issue does get fixed at some point I may well switch over.
Oof. That is not an acceptable way to treat the issue. It’s one thing to say you don’t the time & cycles, but it’s another to WONTFIX it twice with a clear usability problem.
It seems fine to me. They don't want to update it, so they close the issue. They're under no obligation (not even a moral one) to change their plans, and everyone's free to fork it to implement their own plans.
Re: Wayfire 0.8
#7I gave Wayfire a shot a bit earlier in the year, but as I am a Dvorak typist and https://github.com/WayfireWM/wayfire/issues/1601 > is marked as "wontfix", I decided to stick to Awesome for the time being. It did run like a dream, though, even on my ancient potato, so if the keybinding issue does get fixed at some point I may well switch over.
Since the last comment in that thread says there might be some progress at the time of the 0.8.0 announcement, it might be worth asking for an update.
Re: Wayfire 0.8
#8I gave Wayfire a shot a bit earlier in the year, but as I am a Dvorak typist and https://github.com/WayfireWM/wayfire/issues/1601 > is marked as "wontfix", I decided to stick to Awesome for the time being. It did run like a dream, though, even on my ancient potato, so if the keybinding issue does get fixed at some point I may well switch over.
Oof. That is not an acceptable way to treat the issue. It’s one thing to say you don’t the time & cycles, but it’s another to WONTFIX it twice with a clear usability problem.
As the maintainer of Wayfire, I would like to say why I don't consider this a critical issue: the current system allows you to bind actions to a particular physical key. So, no matter what physical keyboard layout and actual layout in software, with the current system, you can bind the action to the desired physical key. Or do people actually want their keybindings to change when they change their layouts?
Re: Wayfire 0.8
#9Anyone using it daily? I'd love to hear about what makes the cool animations.. well, cool. My desktop is pretty boring right now.
I've used Wayfire everyday for a few years now. Although I'm into customisation and tinkering, (so things like Arch, Neovim, and indeed Wayfire, are to my taste), I don't like tiling window managers. I find it's like turning my living room into a workshop. A living space should have sunlight, plants and a sofa to welcome friends. In my opinion wobbly windows and other silly animations are nearer to that kind of organic aesthetic.
Wayfire is a living space I can tinker with.
Re: Wayfire 0.8
#10Earlier quoted context omitted.
Oof. That is not an acceptable way to treat the issue. It’s one thing to say you don’t the time & cycles, but it’s another to WONTFIX it twice with a clear usability problem.
As the maintainer of Wayfire, I would like to say why I don't consider this a critical issue: the current system allows you to bind actions to a particular physical key. So, no matter what physical keyboard layout and actual layout in software, with the current system, you can bind the action to the desired physical key. Or do people actually want their keybindings to change when they change their layouts?
> do people actually want their keybindings to change when they change their layouts?
Personally, yes. If I am in Qwerty and I press the T key, I press the button where T is physically in Qwerty. If I am in Dvorak, I press the button where T is physically in Dvorak. Pressing the button where something is physically in Qwerty when I am in another layout would be very confusing, because effectively it would be that everything else is respecting the layout I am using except this one program that is still using the Qwerty positions of the keys.