Comments by "Mikko Rantalainen" (@MikkoRantalainen) on "Haskell Is Faster Than C | Prime Reacts" video.

  1. 16:00 People often fail to understand how much faster computers are with sequential memory access and arrays win all kinds of data structures as long as the array fits in L1 cache and in many cases even if the array doesn't fit in L1. For details see great video titled "Bjarne Stroustrup: Why you should avoid Linked Lists" I wish the R in RAM actually meant performance.
    1
  2. "With C the most complex data structure is linked list" – all I hear is "skill issue". "You often need garbage collection" – another skill issue.
    1
  3. I'd argue that Rust is the only language you should use for multithreaded code because creating an accidental data race in any other multithreaded language is way too easy. Even with Java, you have to manually mark methods as synchronized or never use any shared memory structures and lose most of the performance win you could have with multithreaded code. With Rust, creating a data race is really hard unless you use unsafe blocks.
    1
  4. X is faster than C assumes that you're discussing about {time to write the code + run the code} instead of {run the code}. Often writing something in C requires more time than equivalent code in some higher level language. However, for me writing Haskell is so slow that I'm more productive with C. On the other hand, I can be more productive with Rust than C.
    1