ElixirWeekly

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

Here's what the latest issue looks like:

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

A Guide to Event Handling in Elixir
Maciej writes about 6 ways of handling events in Elixir and gives a high level overview with trade-offs for each approach.

10 years(-ish) of Elixir
This past weekend, on January 9th, we celebrated 10 years since the first commit to the Elixir repository. José reminisces about what has happened since then.

Extracting LiveView Logic Into LiveComponents
How to extract LiveView logic into a LiveComponent, and how to exchange data both ways.

Elixir in 2021: The Now, The Tomorrow, The Future | Curiosum
Nice article by Michal Buszkiewicz, touching on Elixir 2.0, the philosophy behind the language’s development and its current state in 2021.

How to Connect Pow and Live View in Your Phoenix project
Oliver wrote a short post about connecting Pow and Live View in a Phoenix project.

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