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 #468

This week in Elixir

Popcorn: Bringing Elixir to the Browser
Mateusz describes how you can run Elixir code right in your browser (and which limitations make it unsuitable for production software).

Elixir Background Jobs: Choosing the Right Tool for the Job
Many Elixir background job libraries have come and gone. Paweł tells us why Oban won, plus a practical decision framework for when to consider the alternatives.

Learning Elixir: Tuples
Joa explains how Tuples are like standardized forms where each field has a fixed position and specific meaning.

Even more from around the Elixir community

Elixir Wizards: Nix for Elixir Apps with Norbert (Nobbz) Melzer Podcast

Thinking Elixir: Five Years of Perfect Uptime Podcast

What are state machines? (feat. Ash Framework) Video

The Alchemy of Security: Crafting Secure Applications in Elixir Conference

Nerves Online Meetup Meetup

An Introduction to Oban for Elixir Monitoring Using AppSignal Blog post

Usage Rules: Leveling the Playing Field for AI-Assisted Development Blog post

Building Distributed Cache With Elixir Blog post

Fine-Tuning YOLO to Watch Soccer Matches Blog post

Typhoonworks/usher: Usher is a web Framework-agnostic Invitation Link Management Library for any Elixir Application with Ecto. Project update

#gamedev - Matchmaking System for Elixir Applications, Built on OTP Principles. 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).