
Embrace the pipeline. If C is a sequence of thinly-veiled machine instructions, and Ruby is a sequence of messages between objects, Elm code often takes the form of a sequence of transformations. These are often connected by the |> operator. If you need intuition, think of the UNIX pipe. It’s u…
Elm separates effects, and makes them slightly harder to use, so that computations are easier to write. The reason this works is that most of your code is computation, not effects. There are a few general strategies that help you write computation code:
…ally, Ruby concerns itself with classes, inheritance, objects, and methods. But from what I gather, Ruby is really about the roles objects can play, and dividing responsibilities and knowledge among those roles. It’s about trading dozens or hundreds of lines of procedural code for a collection of coherent, loosely coupled objects and their messages.