'l' aims to be a drop-in runtime for the k and q languages

A new runtime called ‘l’ is positioning itself as a compatible replacement for the k4 and q languages long associated with kdb+ and time-series analytics. The pitch is that existing code runs as-is: the project claims full support for k4 syntax, native q and qSQL, and the core data structures those languages depend on — tables, dictionaries, partitions, and splayed on-disk layouts.

The headline promise is zero code rewrites, which matters in a niche where q/kdb+ codebases are notoriously terse, hard to port, and tied to a costly proprietary stack. Compatibility at the syntax and idiom level, plus an optimized columnar table engine, would let teams keep their query logic while swapping the underlying runtime.

Details on performance, licensing, and how faithfully ‘l’ reproduces edge-case k4 behavior aren’t spelled out in the announcement, and those are the questions that will decide whether it’s a serious alternative or a curiosity. For anyone running q workloads, though, a compatibility-first runtime is a notable development in an ecosystem that has seen few challengers.