[bkeroack]

I like it when kdb is mentioned because then I can post this link: https://github.com/KxSystems/kdb/blob/master/c/c/k.h#L96

It's one of my all-time favorites. A window into a certain type of mind.

[chc4]

I'm surprised you didn't link an actual c file; everything related to k seems to trigger an exorbitantly high number of "what the fuck"s. https://github.com/kevinlawler/kona/blob/master/src/0.c for example.

http://archive.vector.org.uk/art10501320 is one of my favorite articles, though

[RodgerTheGreat]

That article was enough to inspire me to write a K interpreter, and eventually land me a job working with K. If I ever meet Stephen Taylor in person I imagine it'll be an interesting story to tell.

[5jt]

I try to get to most of the Kx Meetups in London.

[kthielen]

That's great that your interest produced that result! When I made a K interpreter, Kx threatened to sue me and everyone I had worked for.

[beagle3]

That’s likely because yours was fast enough to threaten their sales, whereas RodgerTheGreat’s is JavaScript and can not.

Nick Nickolov’s one also disappeared off GitHub, though Kevin Lawler’s Kona k3 implementation and Andrey Zholos’s jitted weird dialect are fast and still up; also nils holm’s klong.

[e12e]

I was kind of happy to find some java code this time around - who says java needs to be verbose?

https://github.com/KxSystems/kdb/blob/master/c/jdbc.java

[smnrchrds]

I imagine this looks more intuitive than normal code to a mathematician: They are no strangers to complex notations and they prefer the brevity they offer.

[yalph]

Sort of a mathematician here, it looks like a disease.

[zie]

Oh my. that's just.. wow. Obviously done before code-review became a standard!

[hakanderyal]

This thread might give some insights about the coding style: https://news.ycombinator.com/item?id=13565743

[pjmlp]

Code-review is a cool thing in SV, trendy startups and the big industry related companies, sadly on most companies whose main business is completely unrelated to IT, just like unit tests it gets a spot just behind writing documentation.