404 karma · joined March 30, 2018
https://meet.hn/city/gb-London
Socials: - github.com/liskin - linkedin.com/in/pivnik - reddit.com/user/Liskni_si
Interests: Cycling, Fitness, Gaming, Hacking, Hiking, Open Source, Outdoor Activities, Programming, Remote Work, Running
---
A slightly longer answer is in a bullet point on our fundraising page (https://github.com/sponsors/xmonad):
> Wayland: It's becoming increasingly clear that the days of X11 are over and some Linux distros are already switching to Wayland. We're committed to keeping xmonad on X11 stable and alive as long as necessary, but if time allows, we should explore the Wayland ecosystem and figure out what it means for xmonad. Do we go all in on waymonad? Shall we try to keep xmonad a pluggable window-management component for another Wayland compositor? Honestly, we don't know yet. This one is a bit of a stretch goal: we might need more than one person full-time to actually make this happen.
Elsewhere in this thread, I wrote about some concerns I have about waymonad and xmonad on Wayland in general: https://news.ycombinator.com/item?id=28796909 The gist of it is that I'd like to keep the compositor and WM separate, because a) xmonad is reconfigured by compiling/restarting, b) I don't think the Haskell runtime is good for handling input and presenting frames, c) I don't want to maintain a compositor :-).
As a maintainer of xmonad upstream, I'm watching the waymonad project to see where it goes, but I have some concerns about its architecture which I'd love to see addressed before we'd officially endorse people to try switching. This is a copy of a message I sent to fellow xmonad developers a couple months ago:
> We should certainly take a look sooner or later. From a quick glance, I have some concerns about the general design of it:
> It's a compositor and window-manager in one. This is typical for Wayland, but there are lots of disadvantages:
> * Restarting the WM is just like restarting X: session over. Unacceptable for xmonad/waymonad, as we don't reload config, we recompile and restart. Someone is apparently working on making Wayland compositors restartable, in general: https://indico.freedesktop.org/event/1/contributions/20/, though.
> * Another consequence of the WM and compositor being one is that they share memory leaks and GC pauses and signal handlers and whatnot. As much as I love Haskell, I'd prefer frames from an FPS shooter to be presented on screen by something else. Oh and did I mention the compositor/WM also handles input, making any GC pauses doubly painful?
> * Aside from operational issues, this also means all of that needs to be implemented. There's https://github.com/swaywm/wlroots/ (used by waymonad), a library that supposedly lets individual Wayland compositors implement less code, but it doesn't seem to be nowhere near what X gives us: we take care of window management and all the input/output handling is taken care of by other tools with their own configuration and tools. It simply doesn't seem to work that way in the Wayland world. There are other options like implementing a shell plugin for Weston, or possibly other libraries, I don't really understand the landscape.
> I may be wrong on some of these, as I didn't actually try to compile and run the thing.
> Anyway, I am convinced it'd be best if the compositor and WM were separate processes, ideally maintained by separate teams. You know, that old “do one thing and do it well” philosophy. And I have no idea how difficult would it be to make things work this way. If someone were to work on this, discovering the answer to this question would be one the first things to do.
I should probably clarify the wlroots handling IO thing: what I meant is that with Xorg, there are command-line tools like setxkbmap, xinput, xset, xmodmap, xcape, xrandr, autorandr and possibly others that a user can use to interact with the X server and tweak stuff, and from what I understand these don't have equivalents in the Wayland world that would work across WMs/compositors. I could be wrong, though, perhaps wlroots does have a standard protocol for such things and such tools already exist?
I'm quite a data nerd, so I wanted to track component wear in more detail than Strava allows. Some people on /r/Strava suggested their online web-based gear trackers, but I was always afraid of trusting them with all the data, and also quite reluctant to enter hundreds of components manually. I really prefer to keep this in git rather than in a 3rd party website that can go away. So now that I have activities metadata in sqlite from strava-offline, it was quite easy to create a local gear tracker that reads rules from YAML and computes component wear. Most of the work was spent polishing this and documenting. :-)
To clarify this further, in https://github.com/xmonad/xmonad/actions/runs/1201348600, GITHUB_RUN_ID=1201348600, GITHUB_RUN_NUMBER=168, but there's no way to get the 3514203530 out of https://github.com/xmonad/xmonad/runs/3514203530 (that's one of the jobs of that run).
||http://abs.twimg.com/fonts/*.woff[1]: https://github.com/git/git/tree/master/contrib/diff-highligh...
And then there's the "little" issue of it not being able to coexist with wee-slack. That's a bug Python 3.9, not in weechat-matrix, but still.
I mean, I still use it because all I really need is chatting in already joined public rooms and for that it's better than that Element/Electron crap, because it's still a weechat after all, but it absolutely is not ready for any kind of serious usage. It's just a quick hack that sort of maybe works, sometimes.
The current keyboard is not really fit to be used as a primary keyboard. A proper 7-row keyboard with full-sized arrows is really a must for people who use laptop keyboards as their main daily driver. Here's a picture of what one looks like: https://imgur.com/Epo5kBw
Please make something like that possible!
function __col1_ps1 {
[[ $MC_SID ]] && return
local termios cur_y
# ask the terminal for any pending (line buffered) input
termios=$(stty --save) && stty -icanon && stty "$termios"
# if there's pending input, assume it's been echoed and we're not in first column
# otherwise ask the terminal for current column and read it from input
if read -t 0 || { IFS='[;' read -s -r -d'R' -p$'\033[6n' _ _ cur_y && [[ $cur_y != 1 ]]; }; then
echo $'\001\033[41m↵\033[m\002\n\001\r\002'
fi
}
PS1='$(__col1_ps1)<the rest of my prompt>'
My full prompt is here: https://github.com/liskin/dotfiles/blob/9785740f7f97d7da1f84...Still, freenode kicked us out anyway this morning. Luckily the Libera staff were able to process our registration quickly afterwards.
The real trick is that Debian packages have sonames in their versions, so ABI compatibility is encoded in package dependencies. So when I try to downgrade a library (to a known older version from snapshot.debian.org), it knows precisely which packages depend on the new version and forces them to be downgraded as well.
This is entirely orthogonal to following upstream vs. backporting patches. Sure, Debian (stable) does backport patches, which makes it more likely that single package downgrades don't downgrade half of the system, but it really is a different thing. Debian testing/unstable follow upstream to a larger extent than Debian stable, and upstream fixes are usually preferred to patch backports. Still, partial upgrades and downgrades almost always work without trouble.
With this issue and Matrix being several times slower than any other instant messenger I've ever seen, I'd really prefer communities didn't move to Matrix. :-/