ElixirWeekly

Get your Elixir News in a weekly email!

Elixir is one of the most vibrant eco-systems in programming right now. There's so much happening and our community is growing faster and faster every day.

ElixirWeekly means: stuff you easily miss, shared on ElixirStatus and the web, handpicked articles and community news in one nice weekly email.

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

Here's what the latest issue looks like:

ElixirWeekly by @elixirstatus

Issue #519

This week in Elixir

Elixir Cluster 101
Johanna shared this practical guide to clustering your nodes and tracking the cluster state for real use cases.

Redesign of Elixir's Homepage
Seems like a long time since Elixir's homepage got a new coat of paint 👀🎉

Hologram Works. Sponsor What Comes Next.
Elixir runs in the browser today, the first applications are in production.Here's where Hologram stands, and how your company can be part of it.

Even more from around the Elixir community

Zig Meets the BEAM: Garrison Hinson-Hasty & Isaac Yonemoto on Safer Native Code Video

Monolith Juice that Looks like Lambda and Tastes like Fast Booting Machines Video

Batching Phoenix LiveView Updates Blog post

Learning Elixir: Error Handling with Try/rescue/catch/after Blog post

cronstrue_ex – Human-readable Cron Expressions in Elixir Project update

B-erdem/belay: A Durable job Engine for Elixir, on Postgres. Jobs are Built from Memoized Steps — Retries Resume Work Instead of Redoing it. Budgets, Workflows, Human-in-the-loop, Embedded Dashboard. 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).