ElixirWeekly

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

Here's what the latest issue looks like:

ElixirWeekly by @elixirstatus

Issue #440

Welcome to Issue #440

Happy 2025!

Another short issue for there wasn't too much going on (except the release of Elixir 1.18, of course).

This week in Elixir

ElixirConf Videos are Up!
Ten new ElixirConf US 2024 videos got posted on Sunday!

Elixir 1.18 Highlights
German took a look at the highlights in the announcement.

Even more from around the Elixir community

Elixir Wizards: Building an Open Vehicle Control System Using Elixir and Nerves with Marc, Thibault, and Loïc Podcast

Learning Elixir: Understanding Atoms, Booleans and Nil Blog post

Create an Address Autocomplete Using Google API, Elixir and Phoenix Liveview Part 2 Blog post

Acalejos/reed: Streaming RSS Reader for Elixir Project update

Agentjido/jido: A Foundational Framework for Building Autonomous, Distributed Agent Systems in Elixir. 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).