Get your Elixir News in a weekly email!

Elixir is one of the most vibrant eco-systems in programming right now. There's so much happening and our community is growing faster and faster every day.

ElixirWeekly means: stuff you easily miss, shared on ElixirStatus and the web, handpicked articles and community news in one nice weekly email.

Every Thursday: No frills, no click-through, no spam.

Here's what the latest issue looks like:

This week in Elixir

Functional Imperative Programming With Elixir
Paul published this great writeup of implementing a while loop in Elixir as a macro.

Lightweight Dependency Injection in Elixir (w/o the Tears)
What are some lightweight ways to do dependency injection in Elixir that don’t require the ceremony overhead of a Behaviour? Let's find out!

Organize Your Functional Code
When coming to a functional language, people often ask, “How do I organize my code?” This blog post takes a look at some ways in which data structures and abstractions can tell us how to organize our modules and functions.

Benchmarking ets Tables vs. GenServers
Devon heard so many people say “ets tables are super fast” without numbers to back it up, so he went out to prove it!

Elixir Pipeline Operators
A small writing on what operators can be used in Elixir for pipelining and how.

That's it for this round, have a great day!
@rrrene from ElixirWeekly

If you like this newsletter, please tell the world!

You can view this issue in your web browser.

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).