ElixirWeekly

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

Here's what the latest issue looks like:

ElixirWeekly by @elixirstatus

Issue #527

Welcome to Issue #527

Hi, sorry for the silence last week, was down with a cold o_O

Here's a recap of what surfaced during that period, we'll be back to our regular scheduling next week 🙂

Even more from around the Elixir community

Is Your Elixir Code Actually Fast? Tobias Pfeiffer on Benchmarking Podcast

Macro Mayhem #5 Podcast

Charts with Plotto Video

Hologram: Building Local-First Apps in Pure Elixir (elixirconf US 2026 Talk) Video

Everything you Missed at ElixirConf US 2026 Video

Set-Theoretic Types from Scratch Conference

Gleam Gathering 2027 Conference

Background Jobs with Oban, Part 1: Stop Blocking Your LiveView Blog post

Debugging a False-Positive Hex Advisory in Elixir CI Blog post

Prepare Once, run in a Fresh VM with SmolBox Blog post

Debugging a False-Positive Hex Advisory in Elixir CI Blog post

Introducing SmolBox: Managing SmolVM Executions from Elixir Blog post

Building Distributed Systems in Elixir: Part 9 - Backpressure Blog post

woylie/ex_icon: Generic Icon Library for Phoenix LiveView Project update

Elue-dev/jev_elixir Project update

Pepe-agent/pepe: An Elixir/OTP AI Agent Runtime: Define Agents, Connect any OpenAI-compatible Model, and run a Tool-calling Loop. CLI, HTTP API, web Dashboard, Telegram, WhatsApp. Project update

Release 0.15.0 · Woylie/doggo Project update

fuelen/seed_factory Released v0.9.0 Project update

Protox 2.1.0 Project update

conradfr/icecast_ex: Read Metadata from Shoutcast & Icecast Streams. 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:

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