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

Here's what the latest issue looks like:

Logo ElixirWeekly by @elixirstatus Issue #157
This week in Elixir

Why Elixir Training?
Desmond Bowe of ElixirTalk fame explains his and Chris' reasons to start Elixir Training.

Running an eInk Display with Elixir, Scenic & Nerves
A blog post going in-depth on some of the details when using our the new Inky library. Some Elixir, some Nerves, some Scenic and if you look under the hood and squint? Some wxWidgets!

Elixir Maps Made Effortless
A short article covering two things that frustrate Elixir learners, especially those coming from a language like JS or Ruby - immutability and the use of strings vs atoms for keys.

Upgrading to Elixir Releases - Live Stream Archive
Archive of Eric’s Elixir live stream from last week, starting to look into upgrading Grapevine for Elixir 1.9 release.

Even more from around the Elixir community

ElixirMix Podcast 059 - Using Rust to Scale Elixir for 11 Million Concurrent Users with Matt Nowack Podcast

Peter Saxton - Raxx.Kit - Lean Mean Web Development for Elixir | Code BEAM STO 19 Video

Phoenix Realtime Chat Application - Setting Up CRUD - Part 1 Video

Testing Phoenix Custom Error Pages Blog post

Released: Statistex 1.0 an Elixir Statistics Calculation Library that Lets you Reuse Previously Calculated Values Blog post

Elixir Resources to Help With Transition to Elixir Blog post

What's new in Horde v0.6.1 Project update

Recase 0.5 version release Project update

Inky library released, version 1.0.0 Project update

open_hours released, version 0.1.0 Project update

gen_rmq 1.3.0 version release Project update

petrovich_elixir 1.0 version release Project update

ecto_autoslug_field@2.0 released Project update

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