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

Here's what the latest issue looks like:

Welcome to Issue #73

This issue is a day late due to a heavy workload these past days.

Sorry for the delay!

This week in Elixir

5 reasons you should use Phoenix instead of Rails
This post is about the 5 reasons that made Elvio switch and why you should consider using Phoenix instead of Rails in your next project!

Using constant pools to speed up your Elixir code
Jacob wrote this brief introduction to module constant pools, colloquially known as the "compile module hack", to increase read throughput and alleviate memory pressure.

Announcing Phoenix in Action!
Geoffrey wrote a book! The new book Phoenix in Action has been released in Manning’s MEAP. Through Nov 28, use the code mllessel to get 50% off.

Robert Virding joins Spawnfest's panel of judges
SpawnFest is a coding contest on the interwebs. You can totally write your projects in LFE, Erlang, Elixir or any other flavor of Beam. Register your team for FREE and win some great prizes!

Ebert for Elixir/Phoenix - First Steps
Let Ebert's code review service help you write better code. Here’s how to get started.

Use the 1.6 code formatter in your browser
The folks at Slab built an in-browser Elixir formatter so everyone can use the new formatter today without installing 1.6-dev.

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