k/q/kdb+ are often touted as having C speed, and the architecture of the interpreter is always cited. In my experience raw performance can be compared to python (or R) for iterative work and numpy for vectorised workloads.
It is an array language and focused on storage and numerical processing of large vector oriented datasets. Its speed as a general programming language is overrated and we often offloaded things to C.
I personally love APL derived languages, but its mystique has fostered a lot of hype.
A simple example, write a for loop with dependent data flow. There is not much optimization.
Get your track record audited and then shop yourself to Chicago prop firms. If things look robust, you should have no problem getting capital on a profit split.
In my opinion, the most tedious part of writing this sort of thing from scratch is the x86/x86-64 instruction encoding. Grab the Intel/AMD manuals or an opcode database and have fun. Other projects to study: LLVM, dynasm, asmjit, peachpy, luajit jit, Intel XED, etc.
Cool. Although the site breaks my back button on Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36
I have a couple of their 6 euro/mo shit boxes and I couldn't be happier. I use them for hosting a couple of small apps, torrent boxes, and IRC bouncers.
Bandwidth to the US sucks, but I didn't expect much more. 10Mb/s on this low spec machine.