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

Here's what the latest issue looks like:

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

Elixir GenServers Memory Issues
Recently, while using Elixir processes (specifically GenServer), Nuno found himself facing an issue that often occurs in other programming languages: the dreaded memory leaks.

Introducing Temple: An Elegant HTML Library for Elixir and Phoenix
Temple is a macro DSL for writing HTML markup in Elixir and a template engine for Phoenix.

Using Select2 with Phoenix LiveView
LiveView doesn’t support JavaScript interop at the moment, so in this article we see how to come up with a workaround to make LiveView playing together with a JavaScript library like Select2.

Slimming down fat Channels in Phoenix
This is a post explaining how Jorge refactored a Phoenix channel module that was getting too complex.

Why Go for Redis when You Can Use Mnesia?
This article covers what happened when introducing Mnesia, including the difficulties encountered and the results achieved.

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