kdb VS cinder

> And later array languages have mostly abandonned the crazy names in favour of actual words

Sharing this without comments:

https://github.com/KxSystems/kdb/blob/master/c/c/k.h

ah, I see you too are a disciple of the kdb school

Ah, after all these years, you've finally found it: a worthy opponent for kdb source code.

I am an experienced developer with 10+ years in various other languages (c++/python/ some scala). I am interested in getting into q/kdb+ after a recommendation from a friend in the industry. Does anyone out there have any suggestions on how to break into the industry Ive done the courses on https://code.kx.com/ and read a few suggested books but cant find any officially recognised certs I could get, and practical experience is limited ! Im not sure even id hire myself into such a role

For the curious, when I first ran into it it looked like this. That is not minified code, it's how people who write K write Java code. It was expected you would take that file and include it in your sources somewhere. The KDB protocol is actually very simple, basically writes out the types with a type tag, length and then the data in binary.

Meta is actually contributing directly to upstream cpython. If you really wanted to, the internal fork is also open source: https://github.com/facebookincubator/cinder

Just one example: last year Meta open-sourced Cinder, which powers Instagram and provides sizeable speedups compared to CPython.

I used to work on the Cinder JIT and can help document any passes you find interesting or confusing.

You might enjoy Cinder then. It's based on CPython so it is nearly 100% compatible.

https://github.com/facebookincubator/cinder/

Disclaimer: I used to work on it.

I think Cinder's Static Python, which also performs runtime type checking, is more ambitious. Though it's not production ready yet.

Here's a fork that implements that https://github.com/facebookincubator/cinder - it might be nice to one day get that up streamed but obviously it'll be controversial and it certainly needs more time to bake. Hopefully at some point we can make it a pip installable extension though.

The other thing that was interesting to me, was the potential of type annotations to help make for a faster, safer experience on the compiler end of things. One example is seen in Meta’s Cinder project, on the docs it explains how typing can be used to reduce the number of steps for the compiler ([cinder/static_python.rst at cinder/3.8 · facebookincubator/cinder · GitHub](https://github.com/facebookincubator/cinder/blob/cinder/3.8/CinderDoc/static_python.rst)), making it more effective.