Book Image

Learning Elixir

By : Kenny Ballou, Kenneth Ballou
Book Image

Learning Elixir

By: Kenny Ballou, Kenneth Ballou

Overview of this book

Elixir, based on Erlang’s virtual machine and ecosystem, makes it easier to achieve scalability, concurrency, fault tolerance, and high availability goals that are pursued by developers using any programming language or programming paradigm. Elixir is a modern programming language that utilizes the benefits offered by Erlang VM without really incorporating the complex syntaxes of Erlang. Learning to program using Elixir will teach many things that are very beneficial to programming as a craft, even if at the end of the day, the programmer isn't using Elixir. This book will teach you concepts and principles important to any complex, scalable, and resilient application. Mostly, applications are historically difficult to reason about, but using the concepts in this book, they will become easy and enjoyable. It will teach you the functional programing ropes, to enable them to create better and more scalable applications, and you will explore how Elixir can help you achieve new programming heights. You will also glean a firm understanding of basics of OTP and the available generic, provided functionality for creating resilient complex systems. Furthermore, you will learn the basics of metaprogramming: modifying and extending Elixir to suite your needs.
Table of Contents (16 chapters)
Learning Elixir
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

With great power...


Although, we've spent an entire chapter on macros and how awesome they are, a word of caution is required. Seldom use macros. That's worth repeating: _seldom_ use macros! Macros have the very real possibility of creating enormous complexity and technical debt—they have the ability to change the core semantics of the language. This can result in very difficult code to read and reason about. Thus, reaching for the macro system should be taken with a great amount of thought. Ask questions and poke the problem, really determine whether using macros is a good choice or not. Several questions may be:

  • Is the problem tractable via macros or can the problem be easily expressed via macros? More so than not using macros?

  • Is there significant overhead on the caller of using macros?

If either of these are answered negatively, it's likely that choosing macros is a bad move.

If both are answered positively, go forth and incur the complexity at the benefit of an elegant solution that may...