Live data from Hacker News

Our experience using Clojure to speed up Beanstalk

blog.beanstalkapp.com

71–75 of 75 posts

Re: Our experience using Clojure to speed up Beanstalk

#71
post #52

Earlier quoted context omitted.

So we can immediately dismiss your "Programs are not meant to be written in idiomatic language. They are meant to resemble the C implementation." claims as baseless . The only example you chose shows programs that manually unroll loops are not accepted. (And that's stated explicitly on the Help page. http://shootout.alioth.debian.org/help.php#unroll )

"... we ask that contributed programs not only give the correct result, but also use the same algorithm to calculate that result." (Except for meteor-contest.)

I'm sure you wish to make a point -- please don't make everyone guess what you mean, just spell it out.

Re: Our experience using Clojure to speed up Beanstalk

#72

Earlier quoted context omitted.

They're optimizing for their business value and resources (programmers) available. It might not impress their programmer friends, but it'll impress their accountant.

Well, in my book using Lisp in production is impressive for the best part of my programmer friends :-)

Two birds, one stone. I think that's what they call in the industry "Experienced". Keep that up.

Re: Our experience using Clojure to speed up Beanstalk

#73
post #71

Earlier quoted context omitted.

"... we ask that contributed programs not only give the correct result, but also use the same algorithm to calculate that result." (Except for meteor-contest.)

I'm sure you wish to make a point -- please don't make everyone guess what you mean, just spell it out.

An algorithm that's idiomatic in one language might be terribly unidiomatic in another. (I'm sure you know this, but) Haskell's pervasive laziness makes some algorithms tractable while requiring a lot of space/time complexity for other algorithms.

Re: Our experience using Clojure to speed up Beanstalk

#74
post #71

Earlier quoted context omitted.

I'm sure you wish to make a point -- please don't make everyone guess what you mean, just spell it out.

An algorithm that's idiomatic in one language might be terribly unidiomatic in another. (I'm sure you know this, but) Haskell's pervasive laziness makes some algorithms tractable while requiring a lot of space/time complexity for other algorithms.

The benchmarks game URL was posted by someone who has put a lot of energy into promoting Haskell - dons makes the best of the opportunity that the benchmarks game provides to promote Haskell.

>>pervasive laziness... requiring a lot of space/time complexity for other algorithmsAnd GHC provides strictness analysis and explicit strictness to avoid reducing performance.

http://www.haskell.org/haskellwiki/Performance/Strictness

Re: Our experience using Clojure to speed up Beanstalk

#75
post #71

Earlier quoted context omitted.

I'm sure you wish to make a point -- please don't make everyone guess what you mean, just spell it out.

An algorithm that's idiomatic in one language might be terribly unidiomatic in another. (I'm sure you know this, but) Haskell's pervasive laziness makes some algorithms tractable while requiring a lot of space/time complexity for other algorithms.

>>I need some sort of shock collar to teach me not to argue about the worth of the Computer Language Benchmarks Game.Do argue - but argue better.

Unfortunately, to argue better does require learning what the website says about the benchmarks game - and for most that's far too much effort.

Post reply on HN