ElixirWeekly by @elixirstatus

Elixir Community News, one email every Thursday.

ElixirWeekly

[ElixirWeekly] Issue #82 - Architecting Flow in Elixir Programs

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

Here's what the latest issue looks like:

This week in Elixir

Binary Parsing Optimizations in Elixir
Elixir Core Team member Aleksei talks about significant part of almost every application, Binary parsing, and how it's done in Elixir.

Architecting Flow in Elixir Programs: An Introduction
Getting the “flow” of a program is one of the first things we can do when looking at open source software or joining a new project at work.

Dynamix Supervisors Replace :simple_one_for_one
Elixir 1.6 replaced the old :simple_one_for_one supervisor strategy with shiny the new DynamicSupervisor module.

Persistent Logins in Elixir with Expected
Jean-Philippe created an Elixir package to enable persistent logins through an authentication cookie, following Barry Jaspan’s Improved Persistent Login Cookie Best Practice.

Comparing Dynamic Supervision Strategies in Elixir 1.5 and 1.6
Andrew compares the changes in dynamic supervision approaches between Elixir 1.5 and 1.6!

Guards in Elixir 1.6
Oscar tells us how he's most pumped about Elixir 1.6's real guard support and compares it to Swift's guards.

[VIDEO] Print Changelog of a Hex Package
What can I say? It does what it says on the package: Prints the changelog for a Hex package.

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

ElixirWeekly provides Elixir community news in a straight-forward, once-a-week email.

Please contact René Föhring (@rrrene) if anything seems broken or worthy of improvement. :-)

Contact | Imprint | Blog