Sarah Jamie Lewis
@sarahjamielewis@mastodon.social  ·  activity timestamp last week

Found some motivation to revisit my zero dep Wayland compositor I started working on last Summer.

Made a number of performance improvements, and fixed a fair number of layout /interaction issues related to popups/sub-compositing so now firefox interaction is much better.

Also added multi-workspace and a debug console and started to link up logs/tracing into that.

Next steps: more debug console options, more performance work and then custom configuration/key binds/layouts.

#wayland #linux

A screen capture of the nyctal compositor showing firefox and a pdf reader windows being interacted with and moved around
A screen capture of the nyctal compositor showing firefox and a pdf reader windows being interacted with and moved around
Lemmus
@Lemmus@social.vivaldi.net replied  ·  activity timestamp last week
@sarahjamielewis Frankly, I salute your bravery. As well as the compositor being useful in itself, perhaps it also can lead to some richer choices for Wayland when people start forking your work? Like 9wm never was that popular on X11, but lead to piles of other WMs when people got something which wasn't too hard to build upon.

Sincerely, somebody who avoids touching both X11 and Wayland programming
Sarah Jamie Lewis
@sarahjamielewis@mastodon.social replied  ·  activity timestamp last week
@Lemmus

> also can lead to some richer choices for Wayland when people start forking your work?

Yeah this is my main motivation. I really want a display server/window manager/etc. that was a lot more flexible and memory safe (and didn't require bringing in large chunks many different code bases as build time/run time deps).