Since a Prof of mine explained the difference between OOP and imperative programming briefly as “the difference is the position of the first parameter”.
Having this in mind, one can think of the . as an alternative of elixirs pipe.
Also paradigms in OOP aren’t about transforming immutable data, but transforming mutable objects, so piping as in elixir might (semantically) not even make sense.
Last but not least, the methods you are calling needs to support chaining into another, but thats the case in elixir anyway. If a method only transforms self and returns Nil you can’t chain it. If a function in elixir just sends a message to modify thats process state and returns a simple :ok you can’t pipe that any further in a meaningful way.
