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

Here's what the latest issue looks like:

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

Keep Your README Install Instructions Up To Date
Bryan shows us how to keep our Elixir install instructions up to date using ExUnit!

Mint, a new HTTP Library by the Elixir Core Team
Eric shows us Mint, a new low-level HTTP client that aims to provide a small and functional core that others can build on top (and that is "low level" as in "does not even have a connection pool").

Soft delete with Ecto 3 and Postgres
One thing that folks sometimes want or need to do is to be able to “soft delete” records in a database. This means that instead of actually removing the record from a database, you in some way keep it there but make it “invisible” to your application.

Binary Pattern Matching in Elixir
Eric shows off how to do binary pattern matching to grab out telnet data that is “out of band" and provides links to the source so you can see the full example!

Locality-sensitive Hashing in Elixir
Learn how to perform fuzzy deduplication of strings using locality-sensitive hashing, and how to make recursive binary pattern matching faster with macros in this post from Leonid.

Announcing Broadway
The goal of Broadway is to significantly cut down the development time to assemble data pipelines, while providing many features and avoiding common pitfalls.

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