ElixirWeekly
Every Thursday: No frills, no click-through, no spam.
Here's what the latest issue looks like:
This week in Elixir
Elixir v1.6.5 has been released
A new version of Elixir has been released! Next to the usual improvements, this release supports the release candidates of Erlang/OTP 21.0.
Elixir Memory - Not Quite Free
Stephen helps those using Elixir to understand the memory allocator and garbage collector that Erlang uses.
Memory Instrumentation in OTP 21
The memory instrumentation module was rewritten for Erlang/OTP 21 to make it
easier to use. In this post John describes the rationale behind the new features
and how to make use of them.
Why I'm Co-organizing The Big Elixir Conference
Bryan, the creator of ElixirScript, is telling us about his journey to become the co-organizer of The Big Elixir in New Orleans on November 8th and 9th.
Plugs Demystified
An entry-level introduction to Plug, in which Hubert shows us how to build a simple website without using Phoenix.
New Version of ElixirJobs with Redesign and Telegram Channel
New version of ElixirJobs has just been released, including a brand new design, easier offer posting and push of new offers to a dedicated Telegram channel.
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 :)
Contact
Feedback? Questions? Anything else?
Please contact René Föhring (email or tweet @rrrene for a quick conversation).
