haskell sounds nice for making things parallel because its all purely functional programming and such but in my experience its incredibly difficult and confusing to actually convince the runtime that you want parallelism instead of laziness
@iitalics this is fun with clojure too!
it seems every time i even touch (future ...) i have to throw (doall ...) calls all around it. bonus points if these futures are created in lazy list comprehension
it's really lovely to have nothing happen until you try to resolve it muuuuch later, and have that thread block until it finishes the work it just started now that you asked for its results
@thingywott yeah i actually saw, on two entirely different occasions, people trying to implement parallel mergesort (which is like the most obviously parallelizable sorting algorithm) and both times they ended up just building a chain of thunks in parallel then all the actual work was performed in one thread at the end