swc VS velox

swc is a wayland compositor library implementation in about 10k sloc.

HOLY SHIT, I spent a couple days playing around, researching wayland, theres a library SWC that implements the core parts of wayland in 10K LINES OF REALLY SIMPLE CODE WITH ALMOST NO DEPENDENCIES.

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).