Hacker News Reader

Comment by Tichy | Hacker News Reader

OK, different attempt then: are there ANY other choices than C/C++ and Java for high performance computing? (No Fortran please, I suppose).

I think there is a fundamental reason why languages with dynamic types will usually be slower than languages with static types, but some statically typed languages should be able to compete in terms of speed?

I suppose that puts Scala and Haskell on the map. I am not a 100% sure about LISP - I think there are variants where static types are optional?

Nitpicking aside, let's assume "pleasant to use" means "deemed cool by the HN crowd". Just give me some suggestions, then I can still decide if I agree or not.

Edit: in the flawed language shootout, Haskell seems to kick ass: http://shootout.alioth.debian.org/gp4/benchmark.php?test=all...

I guess learning Haskell just moved up several steps on my TODO heap.

View on HN

Play around with the Computer Language Benchmarks Game. It's good at showing what some of the trade-offs are. Of course, it's really not very scientific, but it gives you an idea. http://shootout.alioth.debian.org/

You'll usually see C, C++, Java, Haskell, OCaml, Fortran, Scala, and Lisp in the 1-10x range (of the fastest solution). They all should be reasonably competative on most things, and so you might make your decision based on personal preference and available libraries.

This is in contrast to things like Ruby, Perl, and Python which are often take 100x the time.

Thanks - I really need to pick up one of these languages. I know Java well, but don't want to use it anymore. So far I have only tried "slow" alternatives, though. Given my interests (machine learning), sometimes speed is called for.

C# and Ada are typically fast as well (as expected).

Interestingly, Erlang and Lua seem to consistently come out a bit ahead of almost everything else that's not compiled to native code, running on a JITing VM, and/or Lisp.

I have used two varieties of Lisp: Common Lisp and Clojure. Both have dynamic typing with optional "type hints", which allow you to get the performance of a statically typed language. Type hints are typically used only in small doses, for parts of your code that are very performance critical.

>(No Fortran please, I suppose).

I've got a friend who works on simulating air currents around areroplanes real-time. They have to do everything in Fortran but he says that Fortran-99 is actually pretty pleasant. Pretty pleasant compared to older fortrans perhaps :)

> http://shootout.alioth.debian.org/gp4/

Please choose the up-to-date measurements instead of these.

Which ones do you mean?

At the top of

   http://shootout.alioth.debian.org/gp4/

you'll see an "UP-TO-DATE MEASUREMENTS" url

Do you think those labeled "22 Sep 2009" are more up to date than those labeled "mid 2008" or "late 2007"?

If you hadn't said anything, I wouldn't have noticed that these are links. Blame it on the layout of the site.

Did you notice the "PLEASE CHOOSE THE UP-TO-DATE MEASUREMENTS INSTEAD OF THESE!" ?

Haskell does well in benchmarks but this hides the fact that its performance is very unpredictable. Try it and you'll see what I mean. Also, Common Lisp does well in benchmarks but only after a lot of declarations are added which make the code nearly unreadable.

Personally I get the best results from the MLton SML compiler. OCaml is also pretty fast and more practical. YMMV.

Reply on news.ycombinator.com