One Week with Elixir – Language Design Reflections

The author spent a week learning Elixir, motivated by Dave Thomas’s book, and reflects on how the language inherits Erlang’s VM while adding Ruby‑inspired syntax and many ergonomic improvements.

Three "laws" of language design are presented: good designs go unnoticed, bad designs are criticized, and hard‑to‑understand features require repeated explanation.

Elixir files lack an explicit version line, unlike XML; the author argues that source files should declare a version to avoid incompatibilities when language features evolve.

In Erlang, functions are defined as forms, not expressions, which prevents copying module code into the shell. Elixir introduces def to allow function definitions that can be evaluated as expressions.

The extra dot in function calls (e.g., f.(10) ) distinguishes shell‑defined functions from regular calls, a nuance that can confuse newcomers.

The send operator is written as ! in Elixir; the author notes that using the wrong symbol ( <- ) can be a source of syntax errors for developers coming from other languages.

The pipe operator ( |> ) is highlighted as a powerful way to chain function calls, turning code like x(1,2) |> y(a,b,c) into a clear sequence of operations, similar to monadic composition.

Elixir’s sigils allow custom literals; examples include r"..." for raw strings and s"Hello #{A}" for interpolated strings, demonstrating how the language extends the concept of string literals.

Docstrings are recommended to be placed directly above function definitions using the @doc attribute, avoiding detached comments that can lose their association.

Macro quoting ( quote ) and unquoting ( unquote ) are compared to Lisp’s quasi‑quote and comma operators, showing how Elixir simplifies metaprogramming.

Additional syntax quirks such as extra colons in list comprehensions and whitespace rules are discussed, illustrating how minor differences can cause confusing errors.

Closures in Elixir capture immutable variables, contrasting with JavaScript’s mutable closures; the author provides side‑by‑side examples to show why Elixir’s approach leads to more predictable code.

In conclusion, the author finds Elixir’s syntax approachable, its features well‑designed, and believes the language will continue to attract developers, especially given its use in large‑scale systems like WhatsApp.