How to beat kdb+

I’ve recently been pondering how to improve the performance of kdb+. For what it’s worth, I think it’s going to be really hard to beat kdb+ at its “A game”, which is quant-analytics over big data. In a select template: we get free SIMD vectorisation there’s a simple time-and-space analysis tool it’s quick and easy* to write and amend [*] well … maybe not “easy” If we rewrote this in a language…