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

This week in Elixir

FSM Driven Development
A new library by Alexei to manage statefull processes as Finite Automatæ and the impudent proposal for the HTTP verbs extentions.

Elixir LS v0.11.0 released
This version of he Elixir Language Server adds initial support for Elixir 1.14!

Public Database of Elixir Security Advisories
The fine folks at Mirego just launched a new repository which is completely automated and sourced from the GitHub Advisory Database. It is perfect for public usage (while GitHub API requires authentication to fetch security advisories).

Elixir v1.14.0-rc.1 released
This is the last RC before 1.14 - exciting!

Even more from around the Elixir community

Putting LiveView in a Chrome Extension Podcast

Elixir Community Kraków - Meet-up #3 Meetup

Setting User-Agent in Elixir with Finch, HTTPoison, Req, or Tesla Blog post

The Titanic Machine Learning Problem in Elixir Blog post

Fingerprinting Knock Errors for Sentry in Elixir Blog post

Preventing Reuse of the Same Password Blog post

yeshan333/explore_ast_app 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).