payload

If you have problems comparing code, you can adopt the practice of using a diff tool to highlight differences in code for you.

substantiating a scientific argument with a dilbert comic [check]

wasnt smalltalk once a mainstream language? in ancient times, late 80s?

Except then you consider the alternatives :-/

photon to electron in space to photon' to electron on ground ≃ photon to electron on ground

photon to electron (on ground) to battery (filling station) to electron to battery (car) to electron to kinematics VS raw oil (limited on this very planet) to petrol to kinematics

Also not considering resistance loss and petrol transportation. A little bit more complicated :)

Yes, a negative one for this benchmark :)

There is no significant difference in this benchmark. Do you measure something different?

Yes I have and I invite you to do it also by yourself to check it. There is no significant difference in this benchmark between "ghc -O2" and "runhaskell". I didn't investigated why... but I would be very interested in the details :)

Also "-threaded" gives the usual penalty of bookkeeping and bad caching and stuff. You don't need threads in such a benchmark. Though I am mildly surprised that "node" runs faster with multiple processes :)

A haskell version with the Warp server performs just a little bit worse than the go version (6 secs vs 7 secs) with a little bigger minimal latency (68 ms vs 71 ms).

  go version go1.0.2
  runghc 7.6.2
  cabal packages of today

  import qualified Network.Wai as Wai
  import qualified Network.Wai.Handler.Warp as Warp
  import qualified Network.HTTP.Types as HTTP
  import qualified Data.ByteString as ByteString
  import Blaze.ByteString.Builder.ByteString (fromByteString)
  
  main = do
      let port = 8000
      Warp.run port app
  
  app req = do
      let n = 1024*1024
      let bytes = fromByteString $ ByteString.replicate n 100
      return $ Wai.ResponseBuilder HTTP.status200 [] bytes

also excellently documented... not like shake, at first

Thanks for the links! I will definitely use tup for some next project. I try from time to time different make-like systems but I always come back to GNU Make. I also don't fear the GNU Make Reference. But tup looks, again, quite promising. It even has those little context sensitive one-special-char one-letter variables :) But they do something better by design, I see http://gittup.org/tup/make_vs_tup.html

I want to extend this a bit

* scrape your facebook data and most importantly the references to other accounts

* make accessing facebook available through your own software

* when you post something, it should appear on facebook but also directly into the very own self hosted version of your data

Why?

Use facebook but be ready to leave or parallely use one of the many Free Software wanna be social networks.