ElixirWeekly

E-Mail

can't be blank

Making sure you're human: Name your favorite Elixir kernel module!

(can't be blank)

Subscribe

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

Here's what the latest issue looks like:

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.

Even more from around the Elixir community

Thinking Elixir: Embed Friendly Alternative to LiveView? Podcast

Elixir Wizards: Season 9 Finale with Sundi, Bilal, Owen & Dan! Podcast

Bonfire: Building an Extensible Federated Framework with PETALS - Mayel De Borniol Video

Postgres Triggers - PubSub - LiveView Video

Swoosh Gallery Video

TIL: Using Phash2 for Data Partitioning Blog post

Principles of Elixir Application Development Blog post

Elixir Can Make You Avoid The Microservices Architecture Blog post

BartOtten/phoenix_live_favicon: Favicon Manipulation for Phoenix Live View Project update

Submit your blog post/project update

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:

E-Mail

can't be blank

Making sure you're human: Name your favorite Elixir kernel module!

(can't be blank)

Subscribe

Questions & Answers

Yes! Simply post them to ElixirStatus and you can be sure that they land on my radar.

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.

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

Please contact René Föhring (email or tweet @rrrene for a quick conversation).