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

Here's what the latest issue looks like:

Logo ElixirWeekly by @elixirstatus Issue #336
Welcome to Issue #336

Welcome to 2023!

A little maintenance announcement: ElixirWeekly will be changing servers some time this month (probably on a weekend, don't know which one yet).

This week in Elixir

Elixir/Phoenix Security: Denial of Service Due to Atom Exhaustion
In Elixir, unrestricted atom creation is a denial of service vector. Learn how to find and prevent this vulnerability in your Phoenix apps!

Phoenix 1.7 is View-less! đŸ˜±
German wrote a more expanded blog post of his video about the removal of Phoenix.View.

Finitomata Marries Ecto
Aleksei wrote a rant on Business Process Driven Development with Finite Automata.

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