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

This week in Elixir

Polymorphic Embeds in Ecto
Dan shows a simple way to implement polymorphic embeds for virtual fields.

What's New in Elixir 1.16
The fine folks at AppSignal explore the features and improvements in Elixir 1.16.

Careful What Data you Send or how to Tank Your Performance with Task.async
Tobi ran into an interesting problem recently where simple concurrency on the BEAM via Task.async made his application a lot slower and a lot more memory hungry. This blog post illustrates the issue with a short example.

Elixir Streams |> LiveView's Lifecycle Hooks
Ever want to handle a LiveView action (event, message, patch, etc.) across several LiveViews without having to duplicate the code? German's got your back.

Even more from around the Elixir community

Thinking Elixir: FLAME with Chris McCord Podcast

Elixir Wizards: Static Code Analysis in Elixir vs. Ruby with René Föhring & Marc-André Lafortune Podcast

Learning Elixir with ELXPRO - Gustavo Oliveira Video

PSA: Double Check Benchee Benchmarks Made with Elixir Versions 1.14.0 – 1.16.0-rc.0 Blog post

How to Import CSV File to the Database Blog post

Spice up Your LiveView app with a Cool Loading Spinner! Blog post

Phoenix Component Comprehensive Guide Blog post

Woylie/doggo: Collection of Phoenix Components 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).