river

> I think if I was to do a Waylabd compositor, a first step would be to put things like window management beyond an IPC boundary, just like with X. Afaik river does something in that direction https://github.com/riverwm/river > Dynamic layouts generated by external, user-written executables. A default rivertile layout generator is provided. > Scriptable configuration and control through a custom Wayland protocol and separate riverctl binary implementing it.

The most relevant uses of Zig that come to mind are: - Bun, as you mentioned - https://tigerbeetle.com/ - https://www.uber.com/en-IT/blog/bootstrapping-ubers-infrastr... Plus a bunch of other companies (including some very big ones) and projects that use Zig here and there, eg AWS uses cargo-zigbuild https://github.com/awslabs/aws-lambda-rust-runtime/blob/e2d5... Zig also has a few other very promising OSS projects: - https://github.com/riverwm/river (wayland compositor) - https://github.com/ZigEmbeddedGroup/microzig (HAL for embedded development) - https://machengine.org/ (truly cross-platform gamedev) - https://github.com/michal-z/zig-gamedev (another serious gamedev toolkit) Just off the top of my mind. Like for all things, you gotta get started somewhere and this is where we are at the moment.

River does that for the windows layout https://github.com/riverwm/river

FYI the Zig compiler that people are still using today is the C++ one. The self-hosted compiler hasn't been released yet. There's some Zig code running today in the C++ compiler, but hasn't been there for the full life of the project and isn't the main source of bugs by far. To this day I think the top 3 popular Zig projects are Bun, as you mentioned, then River [1] and TigerBeetle [2]. [1] https://github.com/riverwm/river [2] https://github.com/tigerbeetledb/tigerbeetle Up to you to decide how fine is the situation in those projects.

Nothing quite like AwesomeWM yet, but here's two I'm aware of that have some interesting features: https://github.com/WayfireWM/wayfire/wiki https://github.com/riverwm/river (I'm also on Sway, FWIW)

No, the biggest feature of DWM is dynamic window tiling (pretty sure DWM stands for Dynamic Window Manager). Sway/i3 can be made to kinda dynamically tile with scripts, but it's much less consistent, less powerful, and hardly works. They are manual tilers and they don't try to be dynamic tilers. Personally I prefer being able to quickly toggle a dynamic window layout based on my current workflow, and switch back to manual tiling when I specifically need to manually tile. Currently I use Sway too as it's the most mature tiling compositor on Wayland, but once River WM[0], also based on wlroots, matures more I think I will likely make the switch because I often miss dynamic tiling. [0] https://github.com/riverwm/river On a side note, I hate how window moving works in Sway/i3. I can hardly ever get windows to move to where I want them to go w

And I see no purpose in switching to Wayland as long as Xorg keeps working just fine. > If you liked bspwm then you might want to try this: https://github.com/riverwm/river If I wanted to spend time redoing my configuration, maybe, but I have better things to spend my time on. So in however many years it takes before getting Xorg running starts taking more effort than switching. I'm not expecting that to happen anytime soon.

I still see no purpose to do that, with a lot of hacking it would be also possible to make XWayland work with window managers. But that also would be pretty pointless to do because those other parts of the X protocol are also bad and need to be replaced, you might as well just rewrite the window manager. If you liked bspwm then you might want to try this: https://github.com/riverwm/river

This particular example is machine-generated code created by translate-c, it's meant to be semantically equivalent to the C code and even uses language features that you're normally not even supposed to use (c pointers). Reasonable Zig code looks more like this: https://github.com/riverwm/river/blob/master/riverctl/main.z... That said I think it's fine if you don't like the syntax. I think that some complaints are honestly too superficial to be legitimate (like complaining about builtins being prefixed with @), but at the same time Zig is often times prioritizing explicitness over "good looking". I personally consider Swift a very good looking language, but then I look at all the new features that got added since I used it last, remember that I value simplicity over aesthetics, and go back to Zig.

Since various people are asking about xmonad-like tiling in wayland: I wrote Vivarium[0] specifically to be a wayland compositor that behaves exactly like my (fairly simple) xmonad config, but it's a relatively new/unstable compositor and nothing like xmonad internally. River[1] has a fantastic tiling model via user-provided executables, which makes it very flexible and probably a good fit for many people wanting something xmonad-like. Waymonad[2] exists as a direct xmonad-like compositor, but I think development has been basically stalled for a long time. Sometimes there's discussion about reviving it though (edit: see https://news.ycombinator.com/item?id=28796909 for more up to date detail). Japokwm[3] is another compositor with xmonad user roots, but again its own tiling model. [0] https://github.com/inclement/vivarium [1] https://gith

written in Zig, neat. wiki has one of the best lists of base Wayland utilities I've seen: https://github.com/ifreund/river/wiki/Recommended-Software gonna be hard to pry myself off Sway but I ought to try it.

https://github.com/ifreund/river https://www.youtube.com/watch?v=124wdTckHNY