Every Thursday: No frills, no click-through, no spam.
Here's what the latest issue looks like:
This week in Elixir
Case Study: Inky - An eInk Elixir Library
This post is showing the process of porting a python library for a hobbyist eInk display to Elixir. A bit of Nerves, a bit of Scenic, a bunch of refactoring for testability.
Just Enough Erlang
This article explores the more common features with the goal of enabling you to more easily include Erlang libraries in your Elixir projects.
If you need a replicated Redis cluster in Kubernetes, checkout Redex, a cloud-native strong consistent masterless high available Redis implemented in Elixir.
Cleaning up Your Elixir Code
This articles show how you can use hexagonal/ports and adapters/onion layering in order to clean up your Elixir code.
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).