ElixirWeekly

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

Here's what the latest issue looks like:

Issue #74

This week in Elixir

Less than 1 week to go for SpawnFest!
Join us next weekend for a world-wide Beam-based hackathon at SpawnFest! You can win some amazing prizes!

Elixir v1.6 is coming in the next month!
Take a look at what may be in the v1.6 release that's coming in january (hint: it's more than just a formatter).

Beyond Functions in Elixir
Dave shows us how to use advanced language features to refactor existing Elixir code for maintainability.

Introducing PlugCheckup
PlugCheckup provides a Plug for adding simple health checks to your app.

Using Python’s Bitcoin Libraries in Elixir
Paul is currently attempting to learn about the technical details of Bitcoin and blockchains. He blogged about how to use Python’s Bitcoin libraries in Elixir.

Even more from around the Elixir community

ElixirTalk - Drop-in Libraries & Supervisors Podcast

Using Python from Elixir Blog post

Erlang Garbage Collector Blog post

Beyond the Business Case Blog post

The Toy Robot Simulator - Part 2 Blog post

Phoenix & Elm Landing Page - Part 1 Blog post

Quick & Easy Elixir Refactorings - Part 4 Blog post

Released: A Major Update to the Honeybadger Elixir Client! Blog post

observer_cli v1.2.1 released Project update

Compatibility macros for child specifications Project update

Benchee 0.11.0 released Project update

Atom Elixir Formatter 0.4.4 Project update

IntelliJ Elixir v6.7.0 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).

ElixirWeekly by @elixirstatus

ElixirWeekly

Questions & Answers

Contact