Issue #12: BEAM vs Redis, GenStage Patterns and the Elixir Users' Survey 2016
Every Thursday: No frills, no click-through, no spam.
Here's what the latest issue looks like:
This week in Elixir
Elixir Users' Survey 2016
Josh launched the Elixir Users' Survey 2016 this week. He does these every year and while aren't in any way an official thing, I'd like to encourage you to participate (the results are published).
Elixir ETS/DETS/Mnesia/BEAM vs Redis
Redis is becoming an assumed part of many web stacks, in the same breath as your database. But with Elixir, do you need it? Do you even need a database?
Adam shows us some ways he found useful when working with GenStage. Great read!
Pairs.One has been open-sourced
This multiplayer online memory game written in Elixir/Elm has been open-sourced during a lightning talk at EuRuKo!
Ecto.Rut - Ecto Shortcuts to make your life easier!
Ecto.Rut gives you simple wrapper methods that let you directly call CRUD methods from your Module, like `Post.all`.
ElixirConf 2016 videos
Confreaks by now has released a lot of the ElixirConf 2016 videos!
Elixir.LDN 2016 videos
Last, but not least: Video recordings of Elixir.LDN, the London conference, went up on YouTube as well.
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).