Issue #16: How IO Lists help Phoenix be fast, Testing Elixir Apps with ExUnit and Why Ross is Betting on Elixir
Every Thursday: No frills, no click-through, no spam.
Here's what the latest issue looks like:
This week in Elixir
Why I'm betting on Elixir
Ross is looking ahead to web development for the next decade and describes why he's betting on Elixir. Checkout the last section for two more blog posts on the same topic.
Introduction to Testing Elixir Apps with ExUnit
Cody from SemaphoreCI wrote a tutorial on how to introduce test-driven development in Elixir with ExUnit.
Anatomy of an Elixir Process
Let's looks at Elixir's concurrency model and find out how the actor pattern’s actor is an “Elixir Process” in the Elixir programming language.
Visualisation of Elixir Supervision Tree Strategies
Elixir has built in four strategies for supervision trees to enable fault tolerant systems. Enjoy the visualisations …
How IO Lists help Elixir and Phoenix be fast
IO Lists are often just nested lists of strings. But these simple-seeming structures are one of the secrets of efficient IO in Elixir and simple, fast template rendering in Phoenix.
Mocks in Elixir
In this post, Lasse describes how he found "the one way"(tm) to do mocks and describes why it's the one he prefers.
You can subscribe below:
Questions & Answers
Can I submit things I made to be included in the next issue?
Yes! Simply post them to ElixirStatus and you can be sure that they land on my radar.
Is my email address safe with you?
Yes. I'd like to consider myself a trustworthy individual, but then who doesn't?
I am, however, an active member of the open-source Elixir community and the maintainer of Credo and ElixirStatus. I will NOT ruin my reputation by selling your data to a third party.
Why do you require me to confirm my email address?
I just believe that requiring double opt-in to subscribe to any email-based system is a win for both parties: You are safe from unintentionally subscribing and I can be confident that you actually own the email address and want to receive the newsletter I send you :)
Feedback? Questions? Anything else?
Please contact René Föhring (email or tweet @rrrene for a quick conversation).