4 ms·
Just try kdb+/q instead. It’s really the only APL derived language that is used in industry. It’s blazing fast and if you get good at it, you can make more mone
by smabie 7y ago
Just try kdb+/q instead. It’s really the only APL derived language that is used in industry. It’s blazing fast and if you get good at it, you can make more money than maybe any other programming language. It’s a very nice environment and the language (q), comes with a great time series database (kdb+). It’s proprietary, but the 32-bit version is free to use, I believe.
- papercrane 7y ago> It’s proprietary, but the 32-bit version is free to use, I believe. They've changed the licensing a few times. Originally the 32-bit version was free for commercial use, then it became non-commercial use only. Now you can get both the 32-bit and 64-bit versions free for non-commercial use, but you're not allowed to run the free 64-bit version "in the cloud". https://kx.com/connect-with-us/licenses/ https://kx.com/connect-with-us/licenses/
- 7thaccount 7y agoI don't have lots of money and my company passed on it as too proprietary, else I'd be all over it.
- srazzaque 7y agoDid you actually see a quote from Kx before making that decision? I've first-hand seen the cost/proprietary argument thrown into the face of KDB, to then see companies proceed down a path of other technologies, with a 10x spend in hardware and dev effort. KDB is insanely tuned.
- 7thaccount 7y agoThere are other costs. It is hard enough to find people in my industry with domain knowledge, ability to dig into problems, and SQL skills. Finding enough people to use an array language would be difficult as others in my industry have found. I'd personally be super pumped, but I'm an outlier here. Also, there are costs to getting kicked into something like this instead of something like tsdb or influx.