6 ms·
you're doing it wrong: haskell is too slow.
by conformal 13y ago
you're doing it wrong: haskell is too slow.
- zygomega 13y agoI thought so too for a long while, then I tried to do a touch of concurrent code in c++ and had to gouge my eyes out. I'm excited about the speed up haskell brings to development. You can plan things in haskell you can't imagine in other languages.
- conformal 13y agoif concurrency with C/C++ is bad for you, go makes it very easy. however, it is not very fast either. doing it in go and then using cgo where necessary will get you pretty close to C speed.
- NateDad 13y ago+1 for doing it in Go. If concurrency is your objective, Go makes it easy... it's also very fast both to program in and to run.
- cakebread 13y ago> +1 for doing it in Go Conspicuously you don't address Haskell at all. Then again, who cares what might actually be best for OP? There's an advocacy bingo card in play!
- zura 13y agoBut how elegant it is, umm... :)
- z3phyr 13y agoHow much experiance do you have in programming, for claiming that?
- sseveran 13y agoInterestingly I had this exact conversation last week with a guy from an HFT firm that was asking about how do you write fast code in haskell. Haskell won't be as fast as C, but we are not a high frequency shop so it doesn't matter. Much time in engineering at an HFT firm is spent doing things like turning an L2 cache miss into an L1 cache miss. Haskell makes it hard to do things like that. Our platform is fast and could be used for some slower strategies. If we replaced pieces of it with C we could be competitive but probably never less then 10 microseconds wire to wire.
- nilkn 13y agoHaskell is actually quite efficient and tends to be excellent for concurrency.