Home liberachat/#xmonad: Logs Calendar

Logs on 2026-02-03 (liberachat/#xmonad)

00:03:33 <liskin> Actually I specifically preferred Smithay because of Rust.
00:04:03 <liskin> But then my idea has always (a couple years) been to have a separate compositor and window manager.
00:04:39 <liskin> Compositor in Rust/C, talking to the Haskell window manager over some IPC. Could be Wayland protocol, could be whatever else
00:05:45 <liskin> Anyway, geekosaur, do we perhaps have a list of "things people expect from xmonad"? I certainly have an idea of what I expect from it, but I guess other people have very different needs.
00:06:01 <liskin> Would be nice to have a wiki page with these "requirements".
00:08:44 <liskin> My main motivations for the separation of compositor and wm was: latency (no Haskell garbage collection), and ease of development - being able to restart the wm without losing the session, like you can in X11
00:10:10 <liskin> I wonder how people develop their Wayland compositors. I've always worked on the same xmonad that was running my main session. That kind of quick feedback loop is extremely valuable IMO
00:11:57 <liskin> (I have some extra bits in place so even if I screw up and it crashes or goes into a loop, I can still recover - like dumping the state to tmpfs every minute and systemd auto-restarts)
00:13:06 <liskin> Anyway, bedtime now.
00:19:29 <haskellbridge> <g​eekosaur> liskin: someone actually proposed separating them in general and a protocol for doing so. it was soundly thrashed for security reasons iirc
00:20:15 <haskellbridge> <g​eekosaur> as to our requirements list, I think the best we'd do is go through the open issues (here and possibly on the old google issues, which is still there but read only) and collect and probably tag them
00:22:19 <haskellbridge> <g​eekosaur> I think any such separation for xmonad would require a non-wayland private IPC connection
01:14:22 × Digit quits (~user@user/digit) (Ping timeout: 246 seconds)
01:26:50 <haskellbridge> <T​ranquil Ity> liskin: That makes sense
01:26:50 <haskellbridge> If you wanna adapt the reference Smithay compositor for that I can maybe help out, it should serve as a good base despite them wanting to drop it.
01:27:09 <haskellbridge> <T​ranquil Ity> liskin: Embedded Wayland window within another Wayland compositor is the usual way
01:27:23 <haskellbridge> <T​ranquil Ity> Or a separate VT
01:27:36 <haskellbridge> <T​ranquil Ity> At least that's how I did it (both of these)
01:27:42 <haskellbridge> <T​ranquil Ity> * do
01:47:50 Digit joins (~user@user/digit)
06:40:38 <haskellbridge> <d​pn> Tranquil Ity: i haven't thought much about rust <> haskell - but I've mentally always kinda thought traits were somewhat comparable to hs classes :think
06:40:58 <haskellbridge> <d​pn> i haven't thought much about rust <> haskell - but I've mentally always kinda thought traits were somewhat comparable to hs classes 🤔
06:41:00 <haskellbridge> edit: i have no position of authority on the matter - purely vibe
06:43:18 ChubaDuba joins (~ChubaDuba@37.112.231.64)
07:02:58 <geekosaur> there's a few similarities but enough differences that it doesn't make a good mapping
07:14:47 × ft quits (~ft@p508db4c0.dip0.t-ipconnect.de) (Quit: leaving)
08:27:11 Enrico63 joins (~Enrico63@148.252.128.12)
09:48:43 × ChubaDuba quits (~ChubaDuba@37.112.231.64) (Quit: WeeChat 4.8.1)
09:49:01 ChubaDuba joins (~ChubaDuba@37.112.231.64)
09:55:14 × ChubaDuba quits (~ChubaDuba@37.112.231.64) (Quit: WeeChat 4.8.1)
09:55:33 ChubaDuba joins (~ChubaDuba@37.112.231.64)
10:13:32 × ChubaDuba quits (~ChubaDuba@37.112.231.64) (Quit: WeeChat 4.8.1)
10:14:08 <liskin> Security reasons my ass. That's like saying postfix or qmail is less secure than sendmail because they separate functionality into smaller processes.
10:14:11 ChubaDuba joins (~ChubaDuba@37.112.231.64)
10:14:58 <liskin> Sure, doing it the same way as X11 would be insecure. Having a privileged wm communicating over a secure channel is fine.
10:16:20 <liskin> Speaking of that channel - I considered Wayland protocol because I suspected we might need to send some Wayland data structures from the compositor to the WM, and it might just be easier to do over the same protocol. Unless implementing it on the Haskell side is a major pain in the ass.
10:17:37 <liskin> (Note the subtle difference between "protocol" and "channel")
10:19:27 × ChubaDuba quits (~ChubaDuba@37.112.231.64) (Quit: WeeChat 4.8.1)
10:20:26 ChubaDuba joins (~ChubaDuba@37.112.231.64)
10:38:43 <liskin> I think there's also an issue in our tracker where someone's trying to introduce a PureLayout class or something so they can run the layout algorithms as a plugin for some existing Wayland compositor. That's something I'd love to learn more about maybe :-)
10:46:40 × Enrico63 quits (~Enrico63@148.252.128.12) (Quit: Client closed)
10:56:11 Enrico63 joins (~Enrico63@148.252.128.12)
11:30:31 × redgloboli quits (~redglobol@user/redgloboli) (Quit: ...enter the matrix...)
11:32:15 redgloboli joins (~redglobol@user/redgloboli)
12:59:38 × Enrico63 quits (~Enrico63@148.252.128.12) (Quit: Client closed)
14:38:28 Enrico63 joins (~Enrico63@148.252.128.12)
15:20:25 × Digit quits (~user@user/digit) (Ping timeout: 264 seconds)
15:26:32 Digit joins (~user@user/digit)
15:27:17 Digitteknohippie joins (~user@user/digit)
15:28:16 <geekosaur> yeh, not sure what happened with that
15:43:20 × Digit quits (~user@user/digit) (Remote host closed the connection)
15:43:31 × Digitteknohippie quits (~user@user/digit) (Quit: ERC 5.6.0.30.1 (IRC client for GNU Emacs 30.2))
15:47:16 Digit joins (~user@user/digit)
16:02:45 × T_X quits (~T_X@diktynna.open-mesh.org) (Read error: Connection reset by peer)
16:03:24 T_X joins (~T_X@diktynna.open-mesh.org)
17:51:41 × Enrico63 quits (~Enrico63@148.252.128.12) (Quit: Client closed)
18:00:16 ft joins (~ft@p508db4c0.dip0.t-ipconnect.de)
18:16:33 Enrico63 joins (~Enrico63@148.252.128.12)
18:50:15 × Enrico63 quits (~Enrico63@148.252.128.12) (Quit: Client closed)
19:11:35 Digitteknohippie joins (~user@user/digit)
19:12:55 × Digit quits (~user@user/digit) (Ping timeout: 240 seconds)
20:10:23 Digitteknohippie is now known as Digit
22:11:17 Digitteknohippie joins (~user@user/digit)
22:11:29 × Digit quits (~user@user/digit) (Ping timeout: 260 seconds)
22:32:59 Digitteknohippie is now known as Digit

All times are in UTC on 2026-02-03.