waymonad VS velox

I am personally waiting for Waymonad. https://github.com/waymonad/waymonad

It takes time, but the teams behind wlroots etc are doing good work to make sure that wms managed by smaller teams can exist. There are even clones for your specific wm on wayland. See https://github.com/waymonad/waymonad

Why? There's already a port of that specific Wayland manager it's just waiting for someone to either fork it or take it over.

In addition, there was the last commit in 2019. Thus, it can be assumed that the project is dead and therefore nothing will change on the current state. And according to https://github.com/waymonad/waymonad/issues/44, there are probably not enough people who would actively participate in a fork.

OP could try https://github.com/waymonad/waymonad, but it is incomplete, so Sway is likely the better option.

Ideally xmonad would be ported/xmonad devs would be working on waymonad, but I doubt it will happen. Waymonad seems to be abandoned.

Nice to see Qtile on Wayland. But I'm personally waiting for xmonad on Wayland.

https://github.com/waymonad/waymonad

I wouldn't count on it, as Waymonad has not seen active development since 2019 and the Haskell bindings to wlroots have not been updated since 2019 as well. There is a fork, but it has not been active since September 2021. Also, it was based on wlroots, not sway.

That's what the XMonad fans are using: https://github.com/waymonad/waymonad lets you write your Wayland compositor in Haskell, is analogy to the way XMonad lets you write your X window manager in Haskell.

4. The workers (if distributed) or the engine (if single-box) executing the execution plan, by performing the actual computations on actual bytes.

(Note that this is a cartoon version and any given engine will have differences, eg Presto/Trino does not have a clear distinction between LP and Physical Plan.)

1) and 4) are broadly similar across engines, while 2) and 3) vary widely partially because of different requirements (reliability, latency, etc). Projects such as Apache Arrow and Velox (https://github.com/facebookincubator/velox) are making common tools for 4), and as mentioned ANSI SQL, ZetaSQL, Calcite, and Substrait are making common tools for 1).