undefined | Better HN

0 pointssmabie4y ago0 comments

Don't really think this is true. For example had quite a hard time picking up kdb+/q, and none of the tens of languages I had previously encountered really helped much.

0 comments

2 comments · 1 top-level

dnautics4y ago· 1 in thread

you don't suppose there's something specific about kdb/q that makes its difficulty an outlier?

Excel is easy, but if you were restricted to only using the keyboard to use excel, it wouldn't be so easy anymore.

nivertech4y ago

Erlang/Elixir and kdb+/q full-time developer here.

I didn't had difficulty learning kdb+/q. But that's maybe because I had an early exposure to APL (I read a chapter on it in a book as a kid).

Also I had a previous work experience in HPC, data-parallel computations and vectorization/SIMD using the array-programming languages such as Matlab, Octave, R, Julia, etc. And GPU Compute using CUDA/OpenCL.

The really hard to learn part of the kdb is a proprietary frameworks around it. You need them in order to develop a production-grade systems.

j / k navigate · click thread line to collapse