Starting a Project in Ruby and Haskell

Starting a Project in Ruby Frustration "I'll just write a simple script." "Oh, that's a string not a number." "I'll just add some logic to handle this edge case" "Hmm. What does this return?" "Excellent. The test code works. Time to try some real code." "Nothing works." "I've seen these assumptions are unsound." "Well, this is pretty fragile. I should clean this up." "Can we abstract this?" Time Starting a Project in Haskell Frustration "I'll just write a simple script." "OK, I only have 122 lines of code written." "... works?" "I should be honest, I'm just frustrated." "So it's just working?" "I want to know more." "Oh, I messed up. Type b?" "Did I actually know how to program?" "Well that type I typed?" "I'll read CANADA for this?" "But I can't really assume that." "Perhaps this is a monad." "I guess this isn't really a monad then..." "Well that won't typecheck." "Hmm. What datatype best represents this problem?" "Where did everyone go?" "Can we abstract this?" Time

Мем показывает два графика фрустрации при начале проекта на Ruby и Haskell. В Ruby проблемы нарастают постепенно, а в Haskell программист почти сразу погружается в типы, монады и абстракции. Шутка высмеивает репутацию Haskell как сложного языка и обычно используется как реакция на чрезмерно сложный код или внезапно запутанную задачу.

• @profunctor_io / 6526 2021-04-06