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

Here's what the latest issue looks like:

Logo ElixirWeekly by @elixirstatus Issue #314
This week in Elixir

Elixir v1.14.0-rc.0 released
Elixir has a new release candidate! Trying out dbg/2 will be the highlight of this one.

Introducing the Livebook Desktop app
The Livebook desktop app was just launched. Now we can install Livebook on our machine without having Elixir installed before.

The Secretary Problem In Elixir
Todd wrote a little blog post about solving the secretary problem using Elixir.

Components with Dynamic Attributes
Did you know you can dynamically cast LiveView component assigns to HTML attributes?

Even more from around the Elixir community

Thinking Elixir: The End of Localhost Development? Podcast

Elixir Outlaws: The Eternally Nocturnal Programmer Podcast

Bot Defense with Paraxial.io Video

Fixing "Go to Definition" for Elixir's Standard Library Blog post

Using Elixir Telemetry and Tesla Blog post

Data Pipelines in Elixir Blog post

How we Created an In-browser Kubernetes Experience Blog post

How to Build the Simplest Feature Flag System in Elixir & Phoenix Apps Blog post

Elixir Streams, Elasticsearch, & AWS S3 Blog post

Treating Warnings as Errors in Elixir's mix Compile Blog post

Health Status Without log Request Blog post

Getting Rusty with Elixir and NIFs Blog post

Elixir Mock SSE Server Blog post

Elixir Script, What can and Can't be Done Blog post

Using Elixir to Create a Game for Bots Blog post

Recruitee/plug_limit: Rate Limiting Plug Module Based on Redis Lua Scripting Project update

KronicDeth/intellij-elixir v13.2.0 released 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 :)


Feedback? Questions? Anything else?

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