4 ms·
This is a pretty nifty piece of work. Not really a oneliner if it requires a 1/4 page of code, but I'll let it slide :) I do like the concept of keeping I/O in
by 7thaccount 6y ago
This is a pretty nifty piece of work. Not really a oneliner if it requires a 1/4 page of code, but I'll let it slide :)
I do like the concept of keeping I/O in a more traditional language and the matrix/array code in something closer to APL.
- samatman 6y agoThis is why it says one statement, not one line. I've written single-statement argument parsers that take up most of a page of code. I like this because I've barely written more Ruby than APL (none of the latter) but it's perfectly legible to me. I respect the APL family and think the notation-as-a-tool-of-thought camp has a lot going for it. I'm just illiterate in that language.
- deleted 6y ago[deleted]
- userbinator 6y agoNot really a oneliner if it requires a 1/4 page of code, but I'll let it slide I was more surprised by the fact that the GitHub repo containing it actually has quite a few files; I was not expecting it to contain more than 2 or perhaps 3 files.
- smabie 6y agokdb+/q let's you call the server using really any language you would like: https://code.kx.com/q/interfaces/ https://code.kx.com/q/interfaces/ Though, I don't think there's really a problem with just doing I/O in q directly. The theoretical performance won't be as good, but since I/O is, well, I/O bound, it shouldn't really matter. And besides, I bet that even when doing non-array operations, q is faster than Python or Ruby.
- deleted 6y ago[deleted]