ah-

It seems like most features are OSS now.

Optimus etc. use DMA, so you can copy directly between the two devices.

Hopefully looking glass will support that as well in the future. Last time I looked at least nvidias DMA support was officially restricted to quadro only, so not sure it'll actually happen.

What Looking Glass does is take the output picture of that GPU and copy it into a window on your host machine.

Dask can help, but introduces quite a bit of additional complexity.

I'm also looking forward to stricter data models than what pandas currently uses, in particular proper null support for all dtypes and less random type conversion.

https://code.kx.com/q/ref/qsql/ http://www.timestored.com/b/kdb-qsql-query-vs-sql/

There's still a lot left to figure out, even storage formats aren't fully solved.

This would be even better if it didn't need a modified client.

Worth a read.

From looking at the commit history it seems like this is pretty actively developed.

I've tried using more complex tools like vim outliner and evernote, but simple text files work better for me.

A lot of your competitors have, like http://pipeline.ai/, https://github.com/pachyderm/pachyderm and recently https://github.com/polyaxon/polyaxon.

For example, if you want to run the Athena JDBC driver locally or read something from S3 in a longish (>1h) running Python script.

Didn't use XPack or anything fancy though, haven't updated it and the only addon I'm running is https://github.com/lmenezes/cerebro

kubectl apply -f for simple deployments, Helm for more complex ones.

I'd love to use this, many things are so much more straight forward in q than they are in pandas. But if it means noone can run my software unless they pay for kdb+ it's a non-starter.

I wonder if this would work with Kona.

There's https://rocm.github.io/index.html but it's not quite clear to me how far they got and how usable it is today.