Note that the warnings still apply. I have used it continuously since, and there are a few bugs here and there but it mostly works for my use which is very basic, and does e.g. not involve more than a single monitor.
Nothing noticeable. X11 wm's receive high-level events, such as windows opening, closing etc., they're not in-band for anything computationally heavy unlike e.g. Wayland compositors.
Most of my Ruby use is unexpected ;) I don't like Rails, and while I do lots of web dev in Ruby, I think line for line I've written more non-web related Ruby code than web apps.
If you like it, note the X binding is also pure Ruby. Though incomplete it covers most of the important stuff, including enough of XRender to let my (pure Ruby, but translated from a C project) font renderer use it (not used by the wm, but used by my terminal; I really need to clean up the terminal enough to be comfortable pushing the current version of to Github)
I'm the author, and beware that it's still very much "raw". It's extremely minimalist, and I've not even tried to make it feature-complete, that includes not even testing on multiple monitors.
It is the wm I use daily, but I also know where to look if it crashes or otherwise misbehaves.
It definitely has bugs - there's something Chrome does when the file open dialog window opens that makes it sometimes fail to refresh unless I resize it that I haven't bothered tracking down, for example.
Also to add that personally, I moved from i3 to bspwm first, and you might be happier with bspwm than mine in its current state (but thoughtful PR's are welcome)
I had basically two motivations to write my own: 1) because I could, 2) because bspwm - at least at the time had a couple of quirks I disliked: a) if I ran a file manager, it'd open on all the desktops, b) it took a hack that wasn't very satisfying to get one desktop to be floating while the others were tiled. Those were minor, and so if I hadn't already been working on extending X11 bindings for Ruby for my other Ruby projects I probably would've stayed on bspwm, but since my usage was also very simple, I figured I'd see how long I'd last, and I got close enough within a few days to decide it was viable to keep using my own instead of trying to fix bspwm.
My tolerance level for weird quirks that I'm in control of is very high, though. It feels very different when its your own bugs :)
If you want tiling, but i3 requires too much manual work, you might like the more managed layouts that are the default in XMonad: https://xmonad.org/
XMonad works fine with multiple monitors. Each monitor displays one of the many virtual desktops. The normal keys for desktops and for windows work pretty intuitively with multiple monitors.
I am not sure what you want out of I3, but if it is "i3 configuration is too complicated" might I suggest spectrwm. I like it because it hits that sweet spot for a tilling WM between "more configurable than dwm" and "less configurable than i3"
tl;dr
"It currently does not do anything to facilitate working on multiple monitors, as in my current setup I'm only using a single monitor for my Linux machine."
I'm the author, and that's still true. I'd be open to addressing it, but it's not currently a priority for me to work on. I'm moving soon - if my new office gives me space for a second monitor that may change ;)
I'm the author. This was discussed on HN a year ago too:
https://news.ycombinator.com/item?id=39087609
Note that the warnings still apply. I have used it continuously since, and there are a few bugs here and there but it mostly works for my use which is very basic, and does e.g. not involve more than a single monitor.
Build your own window manager in Python:
https://monroeclinton.com/build-your-own-window-manager/
By the way, it is much easier to develop and test these things using VNC, so running an X server in a separate window.
I know very little about window managers, but I know a bit about Ruby, so... Does this have any performance implications?
Nothing noticeable. X11 wm's receive high-level events, such as windows opening, closing etc., they're not in-band for anything computationally heavy unlike e.g. Wayland compositors.
What a unexpected yet exciting project
Most of my Ruby use is unexpected ;) I don't like Rails, and while I do lots of web dev in Ruby, I think line for line I've written more non-web related Ruby code than web apps.
If you like it, note the X binding is also pure Ruby. Though incomplete it covers most of the important stuff, including enough of XRender to let my (pure Ruby, but translated from a C project) font renderer use it (not used by the wm, but used by my terminal; I really need to clean up the terminal enough to be comfortable pushing the current version of to Github)
Diabolical.
This looks rad - I’m getting grumpy at i3 so I’d love to replace it.
Have you used it with multiple monitors by chance?
Thanks for sharing!
I'm the author, and beware that it's still very much "raw". It's extremely minimalist, and I've not even tried to make it feature-complete, that includes not even testing on multiple monitors.
It is the wm I use daily, but I also know where to look if it crashes or otherwise misbehaves.
It definitely has bugs - there's something Chrome does when the file open dialog window opens that makes it sometimes fail to refresh unless I resize it that I haven't bothered tracking down, for example.
Also to add that personally, I moved from i3 to bspwm first, and you might be happier with bspwm than mine in its current state (but thoughtful PR's are welcome)
I had basically two motivations to write my own: 1) because I could, 2) because bspwm - at least at the time had a couple of quirks I disliked: a) if I ran a file manager, it'd open on all the desktops, b) it took a hack that wasn't very satisfying to get one desktop to be floating while the others were tiled. Those were minor, and so if I hadn't already been working on extending X11 bindings for Ruby for my other Ruby projects I probably would've stayed on bspwm, but since my usage was also very simple, I figured I'd see how long I'd last, and I got close enough within a few days to decide it was viable to keep using my own instead of trying to fix bspwm.
My tolerance level for weird quirks that I'm in control of is very high, though. It feels very different when its your own bugs :)
If you want tiling, but i3 requires too much manual work, you might like the more managed layouts that are the default in XMonad: https://xmonad.org/
XMonad works fine with multiple monitors. Each monitor displays one of the many virtual desktops. The normal keys for desktops and for windows work pretty intuitively with multiple monitors.
https://wiki.archlinux.org/title/Comparison_of_tiling_window...
You're spoilt for choice really...
Just as good a time as any to give Sway a try.
I am not sure what you want out of I3, but if it is "i3 configuration is too complicated" might I suggest spectrwm. I like it because it hits that sweet spot for a tilling WM between "more configurable than dwm" and "less configurable than i3"
https://github.com/conformal/spectrwm
Plus I find it handles multiple monitors well.
Have you tried awesomewm? Tbh I never really understood why i3 is so popular and few people seem to mention awesome.
tl;dr "It currently does not do anything to facilitate working on multiple monitors, as in my current setup I'm only using a single monitor for my Linux machine."
I'm the author, and that's still true. I'd be open to addressing it, but it's not currently a priority for me to work on. I'm moving soon - if my new office gives me space for a second monitor that may change ;)